list_commentsFetches the comment thread for a Misar.Blog article by UUID, with pagination controls for limit and offset. Requires an API key and counts against your plan's request quota.
Get the comment thread for an article. Requires an API key; counts against your plan's request quota.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| offset | No | ||
| article_id | Yes | UUID of the article to fetch comments for |
Changes observed during successful MCP inspections.
v5.1.3Input schema / properties / article_id / descriptionPrevious value: -"UUID of the article, as returned in the `id` field by article tools. Not the slug."New value: +"UUID of the article to fetch comments for"Input schema / properties / limit / descriptionRemoved value: -"Comments per page, 1-100. Defaults to 20."Input schema / properties / offset / descriptionRemoved value: -"Comments to skip before this page. Defaults to 0."v5.1.0Input schema / properties / article_id / descriptionPrevious value: -"UUID of the article to fetch comments for"New value: +"UUID of the article, as returned in the `id` field by article tools. Not the slug."Input schema / properties / limit / descriptionAdded value: +"Comments per page, 1-100. Defaults to 20."Input schema / properties / offset / descriptionAdded value: +"Comments to skip before this page. Defaults to 0."v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description usefully adds auth and cost context ('Requires an API key; counts against your plan's request quota'), which is real behavioral information beyond the structured fields.
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 tight sentences with the core action front-loaded and the auth/quota caveat appended. No filler.
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?
With no output schema, the description should carry return-shape and pagination expectations, but it says nothing about ordering, paging, or result structure. It is adequate for a simple read but leaves the limit/offset contract unexplained.
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 33%: article_id is documented in the schema, but limit and offset are undocumented in both schema and description. The description does not compensate by explaining paging or ordering, so it adds no parameter meaning over the structured fields.
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 ('Get the comment thread for an article'), which is clear and distinguishable from reaction siblings like get_reactions. It does not explicitly name an alternative or contrast with a sibling, but the resource scope is unambiguous.
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?
There is no when-to-use guidance, no mention of how this differs from reaction tools or article tools, and no note on pagination behavior despite limit/offset params. The agent is left to infer the context entirely.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.