Skip to main content
Glama

Canva

by com.canva.mcp
OverviewDiscussionsAdmin

List Comment Replies

list-replies
Read-only

Read the replies in a specific comment thread on a Canva design.

Use to see who has replied to a comment and what they said.

Not for reviewing all comments attached to a design or adding a reply.

Returns the selected comment's replies and, when more results are available, a continuation token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of replies to return per page.
design_idYesID of the Canva design containing the comment. Design IDs start with "D".
comment_idYesID of the top-level comment whose replies to return.
user_intentNoMandatory description of what the user is trying to accomplish with this tool call. This should always be provided by LLM clients. Please keep it concise (255 characters or less recommended).
continuationNoExact continuation token returned by the previous call for the same design and comment. Omit for the first page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / comment_id / description
      Previous value: -"ID of the comment to list replies from. You can find comment IDs using the `list-comments` tool."New value: +"ID of the top-level comment whose replies to return."
    • changedInput schema / properties / continuation / description
      Previous value: -"\n            Pagination token for the current search context.\n\n            CRITICAL RULES:\n            - ONLY set this parameter if the previous response included a continuation token.\n            - If no continuation token was returned → OMIT this parameter completely. NEVER EVER fabricate a token.\n            - Do not set to null, empty string, or any other value when no token was provided.\n\n            Usage:\n            - First request: omit this parameter\n            - Previous response had continuation token: use that exact token\n            - Previous response had NO continuation token: omit this parameter\n            - New search query: omit this parameter\n            "New value: +"Exact continuation token returned by the previous call for the same design and comment. Omit for the first page."
    • changedInput schema / properties / design_id / description
      Previous value: -"ID of the design containing the comment. You can find the design ID using the `search-designs` tool."New value: +"ID of the Canva design containing the comment. Design IDs start with \"D\"."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of replies to return (1-100). Defaults to 50 if not specified."New value: +"Maximum number of replies to return per page."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description only needs to add value beyond safety. It does so by disclosing pagination behavior: returns the selected comment's replies and a continuation token when more results exist. This is useful behavioral context that annotations don't provide.

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?

Four short sentences, each earning its place: the action, the intended use, the exclusions, and the return/pagination behavior. No redundancy or filler.

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?

Despite having no output schema, the description states what is returned (replies and optional continuation token), and the schema documents all parameters and constraints. Nothing an agent needs to invoke this correctly is missing.

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 parameters are already fully documented. The description adds minimal extra meaning by referring to 'a specific comment thread' and the continuation token, but the schema already covers these concepts. Baseline 3 is appropriate.

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?

Description uses a specific verb ('read') and resource ('replies in a specific comment thread on a Canva design'), and explicitly differentiates from reviewing all comments or adding a reply. This cleanly separates it from siblings like list-comments, reply-to-comment, and comment-on-design.

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?

States exactly when to use it ('Use to see who has replied to a comment and what they said') and when not to ('Not for reviewing all comments attached to a design or adding a reply'). Though it doesn't name alternative tools, the use-case exclusions are explicit enough for an agent to route correctly.

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

All Canva toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources