Retrieve social posts to review publishing history, scheduled queue items, and current statuses; filter by status or set a result limit for audits and monitoring.
List recent posts in SocialDispatch to see publishing history, scheduled queue items, and statuses.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of posts to return (default: 10, max: 50) | |
| status | No | Filter posts by status |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. 'List' implies a read operation and the description adds that it surfaces history/queue/statuses, but it does not explicitly state read-only safety, permissions, ordering, or pagination behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One front-loaded sentence states the core action and resource with no filler or repetition. It is appropriately sized for a simple list tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a two-parameter list tool with complete schema descriptions and no output schema, the description gives enough context to understand what categories of posts are returned. It could mention ordering or default recency behavior, but the essentials are covered.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the limit and status parameters are already fully documented in the schema. The description adds no parameter-specific semantics beyond the schema, making the baseline 3 appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('List recent posts') plus the scope of what is surfaced: publishing history, scheduled queue items, and statuses. It implies a collection view distinct from get_post_status, though it does not explicitly name sibling alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use the tool—reviewing publishing history or the scheduled queue—but does not give explicit when/when-not guidance or name alternatives such as get_post_status for checking one post. Usage is inferable but not directive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.