lookup_search_filter

What it does

LinkedIn's typed filters take ids, not names. This turns "Berlin" or "Fintech" into the id a precise search needs.

Arguments

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": {
    "type": {
      "type": "string",
      "description": "LOCATION, REGION, COMPANY, INDUSTRY, SALES_INDUSTRY, SCHOOL, JOB_TITLE, JOB_FUNCTION, SKILL, LANGUAGE, SENIORITY, DEPARTMENT, TECHNOLOGIES…"
    },
    "keywords": {
      "type": "string",
      "description": "The name to look up"
    },
    "product": {
      "type": "string",
      "description": "classic (default), sales_navigator or recruiter — the id spaces differ"
    },
    "account": {
      "type": "string",
      "description": "Sender account id or name to act as. Defaults to the healthiest connected account."
    }
  },
  "required": [
    "type",
    "keywords"
  ]
}

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": "lookup_search_filter",
      "arguments": { "type": "LOCATION", "keywords": "Berlin" }
    }
  }'

Returns

{ type, product, items: [{ id, title }] }

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.

{ "type": "LOCATION", "product": "classic", "items": [{ "id": "106967730", "title": "Berlin, Germany" }] }

Worth knowing

Classic and Sales Navigator use different id spaces (LOCATION vs REGION, INDUSTRY vs SALES_INDUSTRY).

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