Skip to main content
Glama

Canva

by com.canva.mcp
OverviewDiscussionsAdmin

List Design Comments

list-comments
Read-only

Browse all comments or threads attached to an existing Canva design.

Use to review feedback, see discussion points, or check mentions.

Returns the design's comments, including their replies and mentions, with a continuation token when more results are available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of comments to return per page.
design_idYesID of the existing Canva design whose comments to return. Design IDs start with "D".
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. Omit for the first page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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. Omit for the first page."
    • changedInput schema / properties / design_id / description
      Previous value: -"ID of the design to get comments for. You can find the design ID using the `search-designs` tool."New value: +"ID of the existing Canva design whose comments to return. Design IDs start with \"D\"."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of comments to return (1-100). Defaults to 50 if not specified."New value: +"Maximum number of comments to return per page."
  2. First observed

TDQS

A4/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 safety profile is covered. The description adds valuable behavioral context beyond annotations: it returns replies and mentions and provides a continuation token for pagination. No contradiction with annotations exists.

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 three focused sentences with the primary action front-loaded, followed by concise use cases and return behavior. There is no filler or redundant repetition of schema details.

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

Completeness4/5

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

For a simple read-only list operation with rich schema documentation and annotations, the description is largely complete: it states the resource, the use cases, return contents, and pagination behavior. The absence of an output schema makes the return-value summary especially useful, though ordering/filtering behavior is not mentioned but is not essential.

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 all four parameters are already documented in the schema. The tool description does not add significant parameter-level meaning beyond the schema, so the baseline score of 3 is appropriate.

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 states a specific verb ('Browse') and resource ('all comments or threads attached to an existing Canva design'), making the tool's function clear. It is distinguishable from mutating siblings like comment-on-design and reply-to-comment, though it does not explicitly name or contrast those alternatives.

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

Usage Guidelines4/5

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

The description gives clear use contexts: 'review feedback, see discussion points, or check mentions.' It does not explicitly state when to avoid this tool or prefer a sibling like list-replies, but the provided use cases are specific enough for an agent to select it appropriately.

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