get_my_profile

What it does

Who the agent is speaking as. Read it before writing in the account's voice.

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": {
    "account": {
      "type": "string",
      "description": "Sender account id or name to act as. Defaults to the healthiest connected account."
    }
  }
}

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": "get_my_profile",
      "arguments": {}
    }
  }'

Returns

{ providerId, fullName, headline, location, publicIdentifier, profileUrl, photo, email, premium, openProfile, organizations }

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.

{ "providerId": "ACoAAB1x…", "fullName": "Marcus Feld", "headline": "Partnerships at Northbeam", "location": "Berlin", "publicIdentifier": "marcusfeld", "profileUrl": "https://www.linkedin.com/in/marcusfeld", "photo": null, "email": "marcus@…", "premium": true, "openProfile": false, "organizations": [] }

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.