Skip to main content
Glama

List draft comments

list_draft_comments
Read-onlyIdempotent

Read the comment threads collaborators and reviewers left on one of the writer's own drafts, with the passage each thread is attached to (quotedText, null for comments on the whole draft). Each comment says whether the writer wrote it (isMine) and whether it is unread. status=open (the default) returns unresolved threads; resolved or all include resolved ones. Threads are newest activity first. Read-only: it does not mark comments read, reply, or resolve threads; the writer does that in the Narrareach editor. Use list_draft_comment_notifications to find drafts with unread comments.

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": {
      "draftId": "<draftId>"
    },
    "name": "list_draft_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum threads to return.
statusNoopen
draftIdYesDraft id from list_drafts or list_draft_comment_notifications.

Output Schema

NameRequiredDescriptionDefault
draftYes
hasMoreYes
threadsYes
truncatedYes
unreadCountYes
openThreadCountYes
connectedAccountNo
notificationsMutedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly, idempotent, and non-destructive annotations, the description discloses ordering (newest activity first), status-filter behavior, quotedText null semantics, and the isMine/unread metadata. It also clarifies the crucial side-effect limitation: it does not mark comments read, reply, or resolve threads.

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?

The description is front-loaded with the core action, then adds status behavior, ordering, side-effect limits, and the relevant alternative. Every sentence carries useful information without repetition.

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?

Given the annotations, input schema, and presence of an output schema, the description covers what an agent needs to invoke the tool correctly and understand its boundaries. It explains thread contents, status filtering, ordering, and the read-only limitation without needing to document return values in detail.

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?

The schema already documents draftId and limit, and the description adds meaningful semantics for status: default open returns unresolved threads, while resolved and all include resolved ones. It does not add much about limit beyond what the schema provides, so it is strong but not fully comprehensive on every 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?

The description states a specific verb and resource: reading comment threads on one of the writer's own drafts, including the attached passage and thread metadata. It clearly distinguishes this tool from list_draft_comment_notifications, which is for finding drafts with unread comments rather than reading a specific draft's threads.

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?

It explicitly identifies the sibling tool to use for finding drafts with unread comments, and it explains that this tool is read-only and does not mark comments read, reply, or resolve threads. That effectively covers both when to use this tool and when the writer must go to the Narrareach editor instead.

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