recent_postsLists your recent posts with per-account status. Check before retrying a failed publish without a post ID to avoid posting twice.
List the user's most recent posts with their status per account. Check it before retrying a publish_post that failed without a post id, so nothing is posted twice.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many posts, newest first. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds real behavioral value beyond that: it discloses that results are per-account status snapshots and frames the tool as a duplicate-prevention check, though it says nothing about pagination or how far back 'recent' reaches.
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?
Two sentences, zero waste. The what (list recent posts with per-account status) is front-loaded and the operational guidance follows immediately.
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?
A one-parameter read tool needs little, and annotations plus the schema cover safety and input semantics; the description covers purpose and the key use case. With no output schema, the exact return shape (fields, ordering, whether account names or ids appear) is only sketched as 'status per account'.
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% and the single 'limit' parameter is already documented as 'how many posts, newest first' with bounds and a default. The description adds no further meaning about ordering, defaults, or what happens at the maximum, so the baseline 3 applies.
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 the user's most recent posts') plus the payload ('with their status per account'), which tells an agent what it gets back. It doesn't explicitly contrast with the closest sibling get_post, but 'most recent' versus a single-post fetch is reasonably inferable.
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?
Gives an explicit trigger condition ('before retrying a publish_post that failed without a post id') and the rationale ('so nothing is posted twice'), naming the sibling it complements. An agent knows exactly when to reach for this instead of blindly re-publishing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.