MisarBlog MCP Server

List comments

list_comments

Read-onlyIdempotent

Fetch the comment thread for a specified article by UUID, using limit and offset to page through reader discussions.

Instructions

Get the comment thread for an article. Requires an API key; counts against your plan's request quota.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "article_id": "<article_id>"
    },
    "name": "list_comments"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`offset`	No
`article_id`	Yes	UUID of the article to fetch comments for

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv5.2.0Nov 7, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / article_id / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

addedInput schema / properties / offset / maximum
```
Added value: +9007199254740991
```

Changed3 schema fields changedv5.1.3Oct 14, 2026

changedInput schema / properties / article_id / description

Previous 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"

removedInput schema / properties / limit / description

Removed value: -"Comments per page, 1-100. Defaults to 20."

removedInput schema / properties / offset / description

Removed value: -"Comments to skip before this page. Defaults to 0."

Changed3 schema fields changedv5.1.0Aug 19, 2026

changedInput schema / properties / article_id / description

Previous 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."

addedInput schema / properties / limit / description

Added value: +"Comments per page, 1-100. Defaults to 20."

addedInput schema / properties / offset / description

Added value: +"Comments to skip before this page. Defaults to 0."

First observedv2.0.0Aug 4, 2026

TDQS

B3.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-annotated behavior: an API key is required and each call burns plan request quota, which matters for an agent deciding how aggressively to page. It still omits whether unauthenticated or private-article cases error, but the auth/quota disclosure is exactly the kind of context annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, with the core action front-loaded and the auth/quota caveat second. There is no filler, though the brevity comes partly from under-specification rather than deliberate economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter read tool with no output schema, the definition is minimally viable: it says what is fetched and what auth costs. But with pagination parameters undocumented in both schema and description, an agent lacks what it needs to iterate a long comment thread correctly, which is a real gap for this tool shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% — only article_id has a description; limit and offset are bare integers with defaults of 20 and 0 and no explanation anywhere. The description never mentions pagination, so an agent cannot learn from it that limit caps at 100 or that offset advances through the thread, and thus it fails to compensate for the low coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Get') and resource ('the comment thread for an article'), so an agent can tell it retrieves comments for a given article. No sibling tool in the list covers comments, so there is little ambiguity to resolve, but it also does no explicit differentiation from adjacent read tools like get_article or get_reactions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'for an article' implies the precondition that an article_id is needed, which is usable context. However, there is no statement of when to prefer this over get_article (which may also return comments) or when-not to call it, and no guidance on paginating when a thread is long.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.