Canva MCP Server

List Brand Templates

list_brand_templates

Discover Canva brand templates available to your account. Apply filters for search, ownership, and sorting to quickly locate the right template.

Instructions

Lists Canva brand templates available to the authorized user.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_brand_templates"
  }
}

Input Schema

Name	Required	Default
`limit`	No
`query`	No
`sortBy`	No	relevance
`dataset`	No	any
`ownership`	No	any
`continuation`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 3, 2026

TDQS

C2.6/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 burden. It implies a read-only operation ('Lists') but doesn't disclose pagination behavior via the continuation parameter, sorting options, or rate limits. It also doesn't describe the return structure or any error conditions.

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?

The description is a single sentence with no fluff, front-loaded with the verb 'Lists.' While concise, it omits important context, so it isn't as helpful as a concise description that includes key behavioral details.

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

Completeness2/5

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

For a tool with 6 parameters and no output schema, this description is severely under-specified. It doesn't mention the continuation token for pagination, filtering capabilities, or the response format. The lack of behavioral context makes it hard to use correctly.

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

Parameters1/5

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

The schema has 6 parameters with 0% description coverage. The description fails to mention any parameters (limit, query, sortBy, dataset, ownership, continuation), leaving their meaning and allowed values entirely unexplained.

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 uses a specific verb ('Lists') and resource ('Canva brand templates'), and adds context ('available to the authorized user'). It distinguishes from siblings like list_presentations by focusing on brand templates, though it doesn't explicitly call out alternatives.

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?

The description provides no guidance on when to use this tool versus alternatives such as search_assets or list_presentations. No usage scenarios, prerequisites, or exclusions are mentioned.

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