Skip to main content
Glama
Sign In
mcp-canva

mcp-canva

by bryankwandou
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

canva_get_pages

Retrieve a list of pages with thumbnails from a Canva design using its design ID. Use it to browse or inspect all pages in a specific design.

Instructions

List the pages of a design with thumbnails.

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": {
      "design_id": "<design_id>"
    },
    "name": "canva_get_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
design_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. 'With thumbnails' hints at return content, but it says nothing about read-only safety, auth requirements, whether thumbnails are URLs or inline data, or pagination behavior for large designs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with the resource and the return-value hint front-loaded. Efficient and readable, though it is arguably too terse given the gaps it leaves.

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

Completeness3/5

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

This is a simple one-parameter read tool with no output schema, so the description needn't explain return values in depth, and 'with thumbnails' partially covers that. However, with zero annotations and zero schema coverage, the definition leaves the identifier semantics and any failure/pagination behavior unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single required parameter (design_id) has no description in the schema. The description only implies 'a design' is referenced, giving no format, source, or constraints for the identifier, so it fails to compensate for the coverage gap.

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 names a specific verb and resource (list the pages of a design) and adds a return-content hint (with thumbnails), which is enough to distinguish it from canva_get_design and canva_list_designs. It stops short of explicitly contrasting itself with those siblings, so it is clear but not maximally differentiated.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus canva_get_design or canva_export, and no prerequisites or exclusions. The agent must infer usage from the name alone.

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

Deploy Server

Other Tools