What it does
The filters a person already tuned in LinkedIn or Sales Navigator, run as-is — no re-encoding of a hundred facets into arguments.
This tool drives a real LinkedIn account
Arguments
| Name | Type | Required | Meaning |
|---|---|---|---|
| url | string | yes | A linkedin.com search results URL, Sales Navigator search or lead-list URL |
| limit | number | no | 1–100 per page |
| cursor | string | no | The `cursor` from the previous page, to continue |
| 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:
{
"type": "object",
"properties": {
"url": {
"type": "string",
"description": "A linkedin.com search results URL, Sales Navigator search or lead-list URL"
},
"limit": {
"type": "number",
"description": "1–100 per page"
},
"cursor": {
"type": "string",
"description": "The `cursor` from the previous page, to continue"
},
"account": {
"type": "string",
"description": "Sender account id or name to act as. Defaults to the healthiest connected account."
}
},
"required": [
"url"
]
}Request
Paste this, swap the key, and you have called the tool.
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": "search_linkedin_url",
"arguments": { "url": "https://www.linkedin.com/sales/search/people?query=(…)", "limit": 25 }
}
}'Returns
{ searchedAs, count, cursor, total, people[], companies[], posts[], jobs[] } — whichever the URL searches.
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.
{ "searchedAs": "Marcus Feld", "count": 1, "cursor": "…", "total": 1840, "people": [{ "providerId": "ACwAAB…", "fullName": "Dana Whitfield", "headline": "CTO at Northbeam", "networkDistance": "DISTANCE_2" }], "companies": [], "posts": [], "jobs": [] }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
search_linkedin_people
Search LinkedIn for people matching an ICP, through a connected sender account
check_reachability
Before reaching out: degree of connection, pending invitation, whether a connection request, a message or an InMail can go to this person — and whether the do-not-contact list or another account of the workspace already covers them
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.