Retrieve a single blog post by numeric ID to fetch its content for editing, review, or display. Use when you need one specific post without listing all blog entries.
Get a single blog post by id.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Numeric id |
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 full burden. 'Get' implies a read-only, non-destructive fetch, which is the key behavioral trait, but nothing is said about behavior when the id does not exist (error vs empty), permissions, or return shape.
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?
A single front-loaded sentence with no wasted words. It is efficient, though its brevity is also part of the reason the usage and behavioral gaps remain.
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 one-parameter read tool with no output schema, the description is minimal but mostly sufficient to call it correctly. It does not describe the returned post shape, and with no output schema available the agent has no other source for that.
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 description coverage is 100% and the single id parameter is fully documented in the schema. The description's 'by id' merely restates the schema and adds no syntax, format, or edge-case detail beyond it.
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?
The description gives a specific verb+resource ('Get a single blog post') and the word 'single' implicitly distinguishes it from the sibling list_posts. However, it never names list_posts/create_post/update_post as alternatives, so it falls short of full sibling differentiation.
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 states what the tool does but offers no when-to-use guidance, no mention of the sibling alternatives (list_posts, get_page), and no prerequisites. The usage context is left entirely to inference from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.