Skip to main content
Glama

Canva

by com.canva.mcp
OverviewDiscussionsAdmin

Get Design Pages

get-design-pages
Read-only

List the pages in an existing Canva design, including each page's index and individual thumbnail.

Use to browse a design's pages or slides, see each page thumbnail in order, show what a specific page looks like, or get a range of page previews. Do not use to retrieve a thumbnail that reflects uncommitted changes in an active editing transaction.

Requires a design with individual pages; Canva Docs do not have pages. Returns only the requested pages, without the design's total page count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of pages to return, from 1 to 100. Use with "offset" to retrieve the next range of pages.
offsetNoPage number to start from. Use for pagination; for example, use 21 to start at page 21.
design_idYesID of the existing Canva design, usually returned by a previous Canva tool. You can also provide a full Canva design share URL, including its collaboration token. Resolve Canva shortlinks before using this field.
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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / design_id / description
      Previous value: -"The design ID to get pages from, or a full Canva design share URL"New value: +"ID of the existing Canva design, usually returned by a previous Canva tool. You can also provide a full Canva design share URL, including its collaboration token. Resolve Canva shortlinks before using this field."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of pages to return (for pagination)"New value: +"Maximum number of pages to return, from 1 to 100. Use with \"offset\" to retrieve the next range of pages."
    • changedInput schema / properties / offset / description
      Previous value: -"The page index to start the range of pages to return, for pagination. The first page in a design has an index value of 1"New value: +"Page number to start from. Use for pagination; for example, use 21 to start at page 21."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark the tool read-only and non-destructive, and the description adds valuable behavioral context beyond that: thumbnails do not reflect uncommitted editing-transaction changes, only the requested pages are returned, and the total page count is not included. This sets accurate expectations without contradicting the annotations.

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, followed by use cases, exclusions, and return limitations. Every sentence earns its place, and there is no redundant restating of the tool name or title.

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?

For a read-only list operation with no output schema, the description sufficiently explains what the agent will get (page index and thumbnail), what it will not get (total page count), and when it is not appropriate. Combined with fully documented parameters and annotations, the agent has enough context to call it correctly.

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 parameters are already well documented; the description adds little parameter-specific detail beyond the notion of ranges and requested pages. Per the baseline for full schema coverage, a 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?

The description opens with a specific verb and resource: 'List the pages in an existing Canva design' and specifies the returned content (page index and thumbnail). It clearly distinguishes itself from sibling get-design-thumbnail by focusing on per-page previews, and it narrows applicability with 'Canva Docs do not have pages.'

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 provides explicit use cases ('browse a design's pages or slides, see each page thumbnail in order, show what a specific page looks like, or get a range of page previews') and explicit exclusions ('Do not use to retrieve a thumbnail that reflects uncommitted changes...' and 'Canva Docs do not have pages'). This tells an agent when to choose the tool and when to avoid it.

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