get_platform_usage

What it does

One roll-up of what this workspace owns and what it has run: installs by target, purchases by status, the hosted seat, the credit balance, and the execution ledger over a window. The platform counterpart to get_usage, which counts LinkedIn calls.

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": {
    "days": {
      "type": "number",
      "description": "Window for the execution counts, 1–365 (default 30)"
    }
  }
}

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_platform_usage",
      "arguments": { "days": 30 }
    }
  }'

Returns

{ window_days, since, installations, purchases, subscription, credits, executions, recent_executions[], note }. Every number is a COUNT over rows this workspace produced.

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.

{
  "window_days": 30,
  "since": 1786492800000,
  "installations": { "active": 2, "removed": 0, "by_target": { "claude": 2 } },
  "purchases": { "pending": 1, "paid": 0, "refunded": 0, "cancelled": 0 },
  "subscription": null,
  "credits": 0,
  "executions": { "queued": 0, "running": 0, "succeeded": 2, "failed": 1 },
  "recent_executions": []
}

Worth knowing

A run is recorded when a LinkedIn tool is called, when a product is installed, and when the outreach engine drafts or sends — so `executions` counts real work, and a failed run carries an error CLASS rather than a provider message. Runs the platform performed itself carry a `product_slug` in the reserved `platform:` namespace, which is not a catalogue slug and has no product page. The `note` field appears only while this workspace has produced no run at all, so four zeroes are never left to read as a slow month. The LinkedIn side of usage — calls, per-tool breakdown and the enforced rate limit — is get_usage, in the other registry.

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.