Skip to main content
Glama

List comments

list_comments
Read-onlyIdempotent

Comments and mentions awaiting a reply, with their status (new, replied, hidden, ignored).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNonew | replied | hidden | ignored
account_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds that mentions are included alongside comments and that results carry a status, but says nothing about ordering, pagination, or the default limit behaviour.

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 tight sentence with the key scoping constraint front-loaded and no filler. It reads as a fragment rather than an action statement, which slightly weakens structure but wastes nothing.

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 read-only list tool with no output schema, the description conveys what is returned at a high level (comments/mentions plus status), which is adequate. It falls short on pagination (limit default 30, max 100) and on what account_id scopes, both of which an agent needs to call it correctly.

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%: `limit` and `account_id` are undocumented in both schema and description, and the status values listed in the description merely restate the one schema-described parameter. The description does not compensate for the coverage gap.

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 names the resource (comments and mentions) and narrows scope to items 'awaiting a reply', with the status values enumerated. It is clear enough to distinguish from reply_to_comment, though it uses a noun phrase rather than an explicit verb like 'list'.

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

Usage Guidelines2/5

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

'Awaiting a reply' implies the use case (finding comments that need a response), but there is no explicit when-to-use statement, no mention of the reply_to_comment follow-up, and no guidance on how status or account filters change the call.

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.

Resources