get_blog_updatesGet latest blog posts from monitored blogs
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Look back N days (default 7) | |
| limit | No | Max items (default 10) | |
| source_id | No | Filter by source ID |
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | Recent blog posts, most recent first |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations cover safety traits (readOnlyHint, idempotentHint, destructiveHint). Description adds contextual detail 'latest' and 'monitored blogs' but no further behavioral info like pagination.
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?
Single sentence, front-loaded, no unnecessary words.
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?
Output schema covers return values. Description is minimal but sufficient for a read-only list tool with full schema descriptions.
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 describes all three parameters with 100% coverage. Description adds no additional param meaning beyond schema.
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?
Clearly states verb 'get' and resource 'latest blog posts from monitored blogs'. Distinct from siblings like get_trending_topics.
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?
No explicit guidance on when to use vs alternatives, but purpose is clear from name and description.
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.