blog_listRead recent blog posts — titles, snippets and ids
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "blog_list"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Optional max number of posts (default all recent) |
Changes observed during successful MCP inspections.
Input schema / properties / limitAdded value: +{
+ "description": "Optional max number of posts (default all recent)",
+ "type": "number"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered. The description adds that it returns recent posts with titles, snippets, and ids, which is useful context beyond annotations. It does not describe ordering or pagination, but for a simple read-only list this is sufficient.
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?
The description is a single concise sentence front-loaded with the primary action and result. No wasted words or redundant information.
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?
The tool is simple (one optional param, read-only, no output schema). The description states the return contents (titles, snippets, ids), which is the key missing information without an output schema. It does not explain whether all recent posts are returned by default, but the schema description covers that. Overall, it is complete for a basic listing tool.
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?
The input schema covers the single parameter 'limit' completely with the description 'Optional max number of posts (default all recent)', so the description adds no additional parameter clarity. Baseline of 3 applies given 100% schema coverage.
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 clearly states the verb 'Read' and the resource 'recent blog posts', and specifies the returned fields 'titles, snippets and ids'. It distinguishes from blog_read by implying a plural listing, but does not explicitly contrast it with blog_read or blog_search.
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 gives no explicit guidance on when to use blog_list vs alternatives like blog_read or blog_search. The context of recent posts is implied but no exclusions or alternative recommendations are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.