social_analytics
Read post analytics for one of the caller's own connected accounts over a window, through the caller's own stored Zernio key. `since` is an inclusive `YYYY-MM-DD` lower bound and Zernio allows at most 366 days. Returns Zernio's `overview` rollup and a `posts` array in Zernio's own shape, because the metric set differs per platform. The account must be on the caller's Zernio profile: an id belonging to someone else answers the same not-found as one that does not exist. Without a stored key the result is `{ code: "integration_required" }` and no call is made.
Read post analytics for one of the caller's own connected accounts over a window, through the caller's own stored Zernio key.
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_analytics", "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
since is an inclusive YYYY-MM-DD lower bound and Zernio allows at most 366 days. Returns Zernio's overview rollup and a posts array in Zernio's own shape, because the metric set differs per platform. The account must be on the caller's Zernio profile: an id belonging to someone else answers the same not-found as one that does not exist. 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.
social_post_cancel
Cancel one of the caller's own posts that has not gone out yet. A draft is marked `cancelled` locally (it never reached Zernio); a scheduled post is also deleted in Zernio, so it will not publish. A post that already published, or one belonging to another user, answers the same not-found as a missing one — Zernio does not let a published post be deleted, and putty does not expose unpublishing. Cancellation is terminal. Runs on the caller's own stored Zernio key; without one the result is `{ code: "integration_required" }` and no call is made.
Trust
A token's trust setup — the modules deployed for it, their controls, and the change log — as a holder reads it.