list_approvals

What it does

What the agent has proposed and what people decided — so it learns which proposals get approved.

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": {
    "status": {
      "type": "string",
      "description": "pending (default), approved, sent, rejected, failed, expired, or decided for everything not pending"
    },
    "limit": {
      "type": "number",
      "description": "1–200 (default 50)"
    }
  }
}

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": "list_approvals",
      "arguments": { "status": "decided", "limit": 20 }
    }
  }'

Returns

{ count, counts, approvals: [{ id, kind, status, target, text, reason, created_at, decided_at, sent_at, error }] }

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.

{ "count": 1, "counts": { "pending": 3, "sent": 12 }, "approvals": [{ "id": "apr_lx3k2a9fq", "kind": "comment", "status": "sent", "target": { "label": "Post by Dana Whitfield" }, "created_at": "2026-10-05T09:00:00.000Z" }] }

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