Retrieve published blog posts by category, language, and pagination. No account or blog permission required.
List published blog posts. No account or blog permission required.
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Requested translation language. | |
| limit | No | ||
| offset | No | ||
| category | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.7Input schema / properties / category / anyOfPrevious value: -[
- {
- "enum": [
- "model-news",
- "engineering",
- "comparison",
- "product"
- ],
- "type": "string"
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "description": "Existing blog category slug: product-updates, tech-sharing (default), product-recommendations, industry-insights, or an administrator-defined category. Legacy aliases product, engineering, model-news and comparison remain accepted.",
+ "maxLength": 32,
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / category / descriptionRemoved value: -"Optional category filter."v0.1.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, and it does disclose the key behavioral trait that this is a public, unauthenticated read. However, it says nothing about pagination behavior (limit/offset defaults), filtering semantics, or result ordering, which matter for a list endpoint.
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 short, front-loaded sentences with no filler. The purpose comes first and the access precondition 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?
An output schema exists, so return values need not be explained, but for a 4-parameter filtered list endpoint with 25% schema coverage the description is too thin. It omits pagination guidance and filter semantics that an agent needs to call this correctly.
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 only 25% (lang and category are described; limit and offset are not), and the description adds no parameter meaning at all. It neither explains filtering by lang/category nor the pagination contract.
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 published blog posts'), which cleanly distinguishes it from the singular sibling acedatacloud_get_blog_post. It does not, however, differentiate itself from other listing siblings like list_announcements or list_showcases.
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 one precondition ('No account or blog permission required') but no guidance on when to choose this tool over acedatacloud_get_blog_post or other listing tools, and no exclusions or alternate paths.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.