---
name: read-social-performance
description: Read Postdom post and account performance while preserving metric availability and evidence gaps. Use when the user asks what published, how a post performed, or which observed posts rank best.
---

# Read social performance with Postdom

Use the Postdom MCP evidence model as returned. Do not fill gaps with estimates.

## Workflow

1. Call get_workspace_status and list_accounts so the answer is scoped to the current workspace and real connected account IDs.
2. Use list_posts when the user asks about scheduled or recent posts without giving a post ID. Preserve its pagination and truncation signals.
3. Use get_publish for the complete outcome of a known post.
4. Use get_performance for one post or one account, never both in the same call. Read the effective window from the response because the workspace plan may clamp the requested history.
5. Use get_best_posts only with a returned account ID, a supported metric, and a supported window.
6. Report a numeric metric only when Postdom returns a numeric value. Preserve the exact availability state: available, delayed(2-3d), estimable, never, or unverified. Also preserve verified_at, evidence, and reason. Never translate an absent value to zero or invent another availability label.
7. Distinguish a provider outcome from Postdom's observation of it. If a state is pending, failed, or partial, do not infer that nothing was published.

Return the source account, post ID when present, observation time, effective window, metric values, and every relevant availability caveat.