get_usage

What it does

What this workspace has spent on LinkedIn this month, broken down by tool. The tool an agent calls to pace itself — cheaper than discovering the rate limit by hitting it, and the only way to see consumption without opening the app.

Arguments

None. Send an empty arguments object.

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": {}
}

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

Returns

month (YYYY-MM, UTC), linkedinCalls, byTool, previousMonth (or null), rateLimit, includedThisMonth and enforced.

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.

{
  "month": "2026-09",
  "linkedinCalls": 412,
  "byTool": {
    "search_linkedin_people": 31,
    "get_linkedin_profile": 298,
    "get_linkedin_posts": 74,
    "list_linkedin_connections": 9
  },
  "previousMonth": { "month": "2026-08", "linkedinCalls": 96 },
  "rateLimit": { "calls": 30, "windowSeconds": 300, "scope": "workspace" },
  "includedThisMonth": 2000,
  "enforced": false
}

Worth knowing

Only LinkedIn tools are counted — workspace tools read our own database and cost nothing, including this one. A call that failed before reaching LinkedIn (no connected account, an unknown sender) is not counted, because you should not be metered for our error message. `enforced` is false today: includedThisMonth is a figure the app displays, not a ceiling the endpoint applies, and we will not start refusing calls past it without saying so first. The limit that does refuse calls is rateLimit.

Limits

No request limit. This tool reads the workspace database and costs nothing to serve. The limits that bite in this product are the sending controls — per-sender weekly invite caps, the warm-up ramp, the working-hours window and a randomised gap between actions — and no tool can raise them.

Related tools

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