get_profile_activity

What it does

What someone engages with says what they care about this month — the most current personalisation signal there is.

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": {
    "profile": {
      "type": "string",
      "description": "Profile URL, public identifier (the /in/ slug) or provider id"
    },
    "kind": {
      "type": "string",
      "description": "comments (default) or reactions"
    },
    "limit": {
      "type": "number",
      "description": "1–100 (default 20)"
    },
    "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": [
    "profile"
  ]
}

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_profile_activity",
      "arguments": { "profile": "ACoAAB1x…", "kind": "comments", "limit": 10 }
    }
  }'

Returns

{ providerId, kind, count, cursor, items }. Comments: { id, postId, text, at }; reactions: { value, postId, commentId }.

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…", "kind": "comments", "count": 1, "cursor": null, "items": [{ "id": "7331…", "postId": "7330…", "text": "Agreed on the observability point.", "at": 1790000000000 }] }

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.