Skip to main content
Glama

Read comments

comments
Read-only

Read the comments under one piece of content. Read-only. Each line: what to pass (a|b: either one), then platforms at 2 credits a call unless numbered. A list of platforms, ids or links: a call each. Failed calls cost 0. Need 100 items? Pass limit=100 (a call a page). Give id: bilibili, facebook, wechat_channels 12, x, zhihu Give id|url: douyin, instagram, kuaishou, reddit, tiktok, weibo, xiaohongshu 12, youtube Give url: wechat 12 With reply_of: bilibili, douyin, instagram, kuaishou, tiktok, wechat 12, wechat_channels 9, weibo, xiaohongshu 12, youtube, zhihu More parameters: capabilities. Pass links whole, as given. On error, follow error.fix. Tell the user billing.display.

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": {
      "platform": "<platform>"
    },
    "name": "comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
urlNo
sortNoOnly bilibili, reddit, xiaohongshu, youtube. By platform: popular, latest, best
limitNoHow many items you want: pages are fetched one after another in this one call until there are that many or no more, each page charged as a call; pages not needed cost 0. Need 100 items? Pass limit=100.
cursorNopage.cursor of the last answer, other arguments unchanged.
handleNoA handle an earlier answer gave, or the request_id of an earlier call: reads that result again, free. Nothing else is run.
platformYesOne, or a list.
reply_ofNo
max_cost_creditsNoRefused, free, if the call would cost more.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sort / description
      Previous value: -"By platform: popular, latest, best"New value: +"Only bilibili, reddit, xiaohongshu, youtube. By platform: popular, latest, best"
  2. Changed1 schema field changed
    • changedInput schema / properties / sort / description
      Previous value: -"By platform: best, latest, popular"New value: +"By platform: popular, latest, best"
  3. Changed2 schema fields changed
    • changedInput schema / properties / handle / description
      Previous value: -"A handle an earlier answer gave: reads that result, free. Nothing else is run."New value: +"A handle an earlier answer gave, or the request_id of an earlier call: reads that result again, free. Nothing else is run."
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "How many items you want: pages are fetched one after another in this one call until there are that many or no more, each page charged as a call; pages not needed cost 0. Need 100 items? Pass limit=100.",
      +  "type": "integer"
      +}
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false), and the description adds real behavioral context beyond them: per-call credit pricing, that failed calls cost 0, that pagination is charged per page, that limit fetches pages sequentially, and that on error the agent should follow error.fix and surface billing.display. The unexplained trailing numbers (12, 9) weaken it slightly, but this is well above the annotation baseline.

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

Conciseness3/5

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

Word count is low and the purpose is front-loaded, but the structure is telegraphic: bare platform lists, an undocumented "a|b: either one" convention, and stray numbers make it slower to parse than a few plain sentences would be. Compactness is achieved at the cost of readability.

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

Completeness4/5

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

For a nine-parameter, multi-platform, no-output-schema tool, the description covers the costly parts: pricing model, pagination, error recovery, and per-platform identifier requirements. It omits output shape detail (no output schema exists) and never defines the numeric suffixes, which is the main remaining hole.

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

Parameters4/5

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

With 67% schema coverage, the description contributes meaning the schema lacks: which platforms accept id, url, or either, which support reply_of, that links must be passed whole as given, and that limit triggers multi-page fetching in a single call. The per-platform footnotes for id|url and reply_of are genuinely additive, though the numbering convention is never 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?

"Read the comments under one piece of content. Read-only." is a specific verb plus resource with an explicit scope limit, so an agent knows exactly what it fetches. It does not differentiate itself from the sibling comment_insights, which is the only real gap.

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?

Guidance is present but embedded in terse platform tables rather than stated as when-to-use rules: it tells you which identifier form each platform accepts and to use capabilities for more parameters. There is no explicit statement of when to choose this tool over comment_insights or search, so usage must be inferred from the platform lists.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.