Skip to main content
Glama

List comments

list_comments
Read-only

Read comment threads for a tela wiki page (full threads) or space (inbox), filter by status, and poll for new or edited activity via cursor.

Instructions

Read comments (editor+). Pass page_id for one page's full threads (each root with its replies), or space_id for an inbox of threads across a whole space (roots only, each with reply_count and page_title — drill into the page for the replies). status is open (default), resolved, or all. TO POLL FOR WHAT HUMANS WROTE: keep the cursor this returns and pass it back as since next time — you then get only threads with new or edited activity, including threads someone replied to, and each comes back with its full context. Anchors are the page's PLAIN TEXT, not its markdown (inline markers stripped, blocks joined by single newlines), so match anchor_exact loosely against a get_page body rather than searching for it verbatim. Answer a thread with add_comment(parent_id=…) and close it with update_comment(resolved=true).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNomax threads (default 50, max 200)
sinceNoopaque cursor from a previous call; returns only threads with new or edited activity since then
statusNoopen (default) | resolved | all
page_idNopage whose threads to read (root + replies); give this or space_id, not both
space_idNospace whose open threads to read as an inbox (roots only, with reply_count and page_title); give this or page_id, not both

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNopass back as since on the next call to see only what changed
threadsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.11.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/non-destructive, and the description layers on real behavioral context: editor+ permission requirement, roots-vs-replies shape difference between the two modes, cursor polling semantics including edited-activity and full-context returns, and the anchor plain-text caveat. These are traits the annotations do not cover.

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?

Front-loaded with the core verb, then modes, polling pattern, anchor caveat, and related tools in a logical sequence. Despite its length, every sentence carries operational meaning and none restates the schema verbatim.

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

Completeness5/5

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

With an output schema present, return values need no explanation, yet the description still clarifies the shape difference between modes. Combined with annotations covering safety, nothing an agent needs to call this correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds value by tying page_id/space_id to their result shapes ('drill into the page for the replies') and framing since as a cursor-returned polling token. The anchor explanation enriches result interpretation though it maps to no parameter.

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

Purpose5/5

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

States a specific verb+resource ('Read comments') and immediately distinguishes the two operating modes: page_id for full threads (root + replies) vs space_id for a cross-space inbox of roots only. An agent can tell this apart from sibling reads like get_page or search without opening the schema.

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

Usage Guidelines5/5

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

Explicitly says which parameter selects which behavior, what status values mean, how to poll with cursor→since, and routes follow-up actions to add_comment(parent_id=…) and update_comment(resolved=true). This is when-to-use guidance plus named alternatives.

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