Analytics Report
Use the bundled PostPeer MCP tools for live analytics. Never retrieve credentials from the user's machine or ask the user to paste a secret into chat. If authentication fails, direct the user to update the PostPeer API key in Claude's plugin configuration UI.
Routing
- Single PostPeer post: call
get_analyticswithpostId. - Recent PostPeer posts: call
get_analyticswithfromDate,toDate, sorting, pagination, and an optional platform. - Direct platform account analytics: call
get_analyticswithsource: "platform",platform, andaccountId. - External platform post ID: include
platformandaccountIdso PostPeer can resolve it. - If the connected server advertises a more specific analytics tool for the requested platform, use that documented tool rather than inventing parameters.
Workflow
- Resolve the date range to absolute
YYYY-MM-DDvalues and state the timezone used. - Resolve account IDs with
list_integrationswhen needed. - Fetch analytics with the narrowest MCP query that satisfies the request.
- Sort by the requested metric when supported: date, likes, comments, impressions, views, shares, saves, clicks, or engagement.
- Report the key result, data limitations, and a useful next action.
Caveats
- Platform APIs differ. Do not compare views and impressions as if they were identical.
- Some platforms expose delayed, sampled, or partial metrics.
- If a published platform post cannot be matched, report that resolution is needed instead of fabricating metrics.
- Reading analytics is non-destructive. Confirm before any follow-up action that changes posts, accounts, or notification settings unless the user explicitly requested it.


