Skip to main content
Glama

get_comments

Read top-level comments from Zhihu questions, answers, or articles by URL, with an optional count to limit results for review or analysis.

Instructions

Read top-level comments for a question, answer, or article.

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": {
      "url": "<url>"
    },
    "name": "get_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
countNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. "Read" signals a non-mutating operation, but nothing is said about ordering, pagination behavior, whether a default count truncates results, or any auth requirement for private content.

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?

A single well-formed sentence with no filler, and the scope-defining word "top-level" is front-loaded. It is arguably too terse given two undocumented parameters, but there is no wasted wording to trim.

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?

The output schema handles return values, so the description needn't explain them. However, for a tool with no annotations and zero schema description coverage, it leaves the count parameter and any paging/filtering behavior entirely unexplained.

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 0% with two parameters, so the description must compensate. It does clarify that the url may point to a question, answer, or article, which adds real meaning, but the count parameter (default 20) is never mentioned or explained.

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?

States a specific verb and resource ("Read top-level comments") and scopes it to three target types (question, answer, article). The qualifier "top-level" implicitly separates it from get_comment_replies, though it does not name that sibling.

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?

Usage is implied rather than stated: an agent can infer this is the tool for comments on a single item once it has a URL, and that replies require a different call. There is no explicit when-to-use/when-not-to-use guidance or prerequisite note.

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