putty
MCPSocialPublishing

social_accounts_list

List the social accounts connected in the caller's own Zernio account. Runs on the caller's own stored Zernio key — putty has no Zernio account of its own and pays nothing, so the connected accounts and every post are billed to the caller's Zernio account. Returns `{ profileId, profileCandidates, accounts }`. `profileCandidates` is non-null only when the account has several Zernio profiles and none has been chosen: the user picks one on the Integrations page. With one profile it is used automatically; with none, putty creates one named "putty". Without a stored key the result is `{ code: "integration_required" }` and no call is made.

List the social accounts connected in the caller's own Zernio account. Runs on the caller's own stored Zernio key — putty has no Zernio account of its own and pays nothing, so the connected accounts and every post are billed to the caller's Zernio account.

Input

The tool takes a single JSON object. Every field, its type, and an example are on the generated reference at GET /mcp/tools, under this tool's name.

Calling it

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": { "name": "social_accounts_list", "arguments": {} }
}

Put your arguments in place of the empty object. A call that fails comes back as a normal result carrying isError: true and a message naming what went wrong, not as a JSON-RPC protocol error.

Notes

Returns { profileId, profileCandidates, accounts }. profileCandidates is non-null only when the account has several Zernio profiles and none has been chosen: the user picks one on the Integrations page. With one profile it is used automatically; with none, putty creates one named "putty". Without a stored key the result is { code: "integration_required" } and no call is made.

The full request and response shape, and a live playground, live on the generated reference at GET /mcp/tools.

On this page