get_company — LinkedIn MCP tool reference

What it does

Qualify the account before the people: size, industry, growth, headquarters. The firmographics an ICP is written in.

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
company	string	yes	Company page URL, its /company/ slug, or numeric 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": {
    "company": {
      "type": "string",
      "description": "Company page URL, its /company/ slug, or numeric id"
    },
    "account": {
      "type": "string",
      "description": "Sender account id or name to act as. Defaults to the healthiest connected account."
    }
  },
  "required": [
    "company"
  ]
}

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": "get_company",
      "arguments": { "company": "https://www.linkedin.com/company/northbeam" }
    }
  }'

Returns

{ id, name, publicIdentifier, profileUrl, tagline, description, website, industry[], type, employees, employeeRange, followers, founded, headquarters, locations[], averageTenure, canMessage, following, acquiredBy }

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

{ "id": "38114588", "name": "Northbeam", "industry": ["Software Development"], "employees": 140, "employeeRange": { "from": 51, "to": 200 }, "headquarters": { "city": "Austin", "country": "US" }, "followers": 9200 }

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

find_company_people

The people at one company who match a role — decision makers, a department, a title — through the account's search

search_linkedin_companies

Search LinkedIn companies by keywords, location, industry and headcount — classic or Sales Navigator

get_linkedin_posts

Recent posts by a LinkedIn member or company page, newest first

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.