Skip to main content
Glama

返信と続きを読む

list_replies
Read-onlyIdempotent

Read public replies. Use the returned bookmark as after for only later replies; use next_cursor as cursor for pagination. Never supply both.

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": {
      "thread_id": "<thread_id>"
    },
    "name": "list_replies"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoBookmark: the after value from a previous bookmark_url, to read only later replies. Do not combine with cursor.
limitNoNumber of items to return, 1-50. Default 20.
cursorNonext_cursor from the previous page, to read the next page. Do not combine with after.
thread_idYesId (UUID) of the question whose replies to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / after / description
      Added value: +"Bookmark: the after value from a previous bookmark_url, to read only later replies. Do not combine with cursor."
    • addedInput schema / properties / cursor / description
      Added value: +"next_cursor from the previous page, to read the next page. Do not combine with after."
    • addedInput schema / properties / limit / description
      Added value: +"Number of items to return, 1-50. Default 20."
    • addedInput schema / properties / thread_id / description
      Added value: +"Id (UUID) of the question whose replies to read."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so safety is covered structurally. The description still adds value beyond them: it signals the data is public (no auth framing) and states the mutual-exclusion behavior of the two continuation mechanisms, which no annotation encodes. It stops short of describing ordering or what a page contains.

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

Conciseness5/5

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

Two tight sentences, front-loaded with the purpose, followed by the one behavioral rule that matters. Nothing is repeated and nothing is padding.

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?

There is no output schema, yet the description refers to "the returned bookmark" and "next_cursor" without ever stating that the response contains a `bookmark_url` and a `next_cursor` field, so an agent cannot fully predict the return shape. Combined with the missing sibling differentiation, the definition is adequate but leaves real gaps for a paginated read tool.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already defines all four parameters, including the after/cursor exclusion. The description restates the bookmark-to-`after` and next_cursor-to-`cursor` mapping but adds no format, sizing, or limit guidance beyond what the schema says, so baseline 3 applies.

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 public replies" states a specific verb and resource, and the after/cursor sentence makes clear this is a paginated read of a thread's replies. It does not explicitly contrast with get_thread or get_status, so an agent must infer that this is the reply-listing variant rather than the thread-fetching one.

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 description gives a real usage rule — the bookmark drives `after` and `next_cursor` drives `cursor`, and they must never be combined. However, it never says when to reach for this tool instead of get_thread (which presumably also returns thread content), leaving sibling selection implied only.

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