check_reachability — LinkedIn MCP tool reference

What it does

Decide the first touch before proposing it: invite, message, InMail, or leave them alone. One call answers what LinkedIn allows and what this workspace's own rules allow.

This tool drives a real LinkedIn account

It runs through a connected sender account in your workspace — not through a scraper and not through your own profile. Call list_sender_accounts first to see which identities are connected and healthy. If the workspace has none, this tool returns an error telling you so; accounts for agents covers how teams get one without risking their own profile.

Arguments

Name	Type	Required	Meaning
profile	string	yes	Profile URL, public identifier (the /in/ slug) or provider id
account	string	no	Sender account id or name to act as. Defaults to the healthiest connected account.

This table is generated from the literal inputSchema that tools/list returns, so what your client sees and what this page says are the same object:

inputSchema

{
  "type": "object",
  "properties": {
    "profile": {
      "type": "string",
      "description": "Profile URL, public identifier (the /in/ slug) or provider id"
    },
    "account": {
      "type": "string",
      "description": "Sender account id or name to act as. Defaults to the healthiest connected account."
    }
  },
  "required": [
    "profile"
  ]
}

Request

Paste this, swap the key, and you have called the tool.

curl

curl -s https://topclozer.com/api/mcp \
  -H "Authorization: Bearer tcz_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "check_reachability",
      "arguments": { "profile": "https://www.linkedin.com/in/example" }
    }
  }'

Returns

{ target, networkDistance, pendingInvitation, canInvite, canMessage, canInmail, openProfile, blocked: { doNotContact, duplicate }, recommended }

The payload arrives inside an MCP content block — one text block whose body is this JSON, pretty-printed. Parse the string; there is no structured-content field.

payload

{ "target": { "name": "Dana Whitfield", "providerId": "ACoAAB1x…" }, "networkDistance": "DISTANCE_2", "pendingInvitation": null, "canInvite": true, "canMessage": false, "canInmail": true, "openProfile": false, "blocked": { "doNotContact": null, "duplicate": null }, "recommended": "propose_connection_request" }

Rate limit

30 LinkedIn tool calls per 5 minutes, per workspace. Exceeding it returns HTTP 429 with JSON-RPC error -32002 and a Retry-After header. The budget is shared by every LinkedIn tool and counted per workspace, so minting a second key does not buy a second allowance.

The limit exists because an agent retrying in a loop is the request pattern that gets a LinkedIn account restricted, and a restricted account is a much worse outcome for you than a 429. Workspace tools do not spend this budget.

Related tools

propose_connection_request

Propose a LinkedIn connection request. It is NOT sent: it waits in the workspace's Approvals queue until a person approves it, then goes out under the account's Smart Limits.

propose_message

Propose a LinkedIn message to a 1st-degree connection. It is NOT sent: it waits in Approvals until a person approves (and may edit) it.

propose_inmail

Propose an InMail to someone outside the account's network. NOT sent: it waits in Approvals. Spends an InMail credit when sent, unless the person has an Open Profile.

All 65 tools are listed on the tool index. Connecting a client is on the Claude setup page, and the protocol details are on the server page.