Tool reference · LinkedIn

list_linkedin_connections

First-degree connections of a connected sender account

read-onlyreaches LinkedInrate limited

Updated 2026-09-18 · Server 2.0.0

What it does

Who a connected account already knows. Used to find a warm path into a company, and to tell an agent which people it does not need to ask for an introduction to.

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

NameTypeRequiredMeaning
limitnumbernoHow many connections, 1–200 (default 100)
accountstringnoSender account id or name.

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": {
    "limit": {
      "type": "number",
      "description": "How many connections, 1–200 (default 100)"
    },
    "account": {
      "type": "string",
      "description": "Sender account id or name."
    }
  }
}

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": "list_linkedin_connections",
      "arguments": { "limit": 100 }
    }
  }'

Returns

{ account, count, connections }. Each connection: memberId, firstName, lastName, headline, publicIdentifier.

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
{
  "account": "Marcus Feld",
  "count": 1,
  "connections": [
    {
      "memberId": "ACoAAB1x…",
      "firstName": "Dana",
      "lastName": "Whitfield",
      "headline": "CTO at Northbeam",
      "publicIdentifier": "example"
    }
  ]
}

Worth knowing

This is the network of the sender account, not of the person signed into the app — on a managed account they are different networks, and that distinction matters when an agent reasons about "do we know anyone there". memberId is the same handle the other LinkedIn tools take.

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

All 21 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.