Skip to main content
Glama
Unified Canva Skills MCP Server

Unified Canva Skills MCP Server

by JehadurRE

canva_get_layout_spec

Retrieve exact dimensions, safe margins, bleed, grid columns, and typography specs for any Canva design format to set up layouts correctly.

Instructions

Return exact dimensions, safe margins, bleed, grid columns, and typography specs for any Canva design format (social, presentations, posters, reports, magazines, business cards).

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": "canva_get_layout_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
presetNoFormat preset ID, or omit to use us-letter-3col.us-letter-3col
list_allNoIf true, returns a summary list of all supported format presets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Return' correctly signals a read-only lookup and the enumerated fields tell the agent what comes back, but it says nothing about whether the values are static presets versus design-specific, nor anything about auth or rate limits.

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?

A single front-loaded sentence with the primary output list first and parenthetical examples last. The examples earn their place by showing the range of covered formats, and there is no filler.

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?

There is no output schema, so the description must enumerate return values, and it does so directly (dimensions, margins, bleed, grid, typography). For a two-parameter, zero-required lookup tool this is close to complete, with the only shortfall being absent guidance on which preset to choose.

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

Parameters4/5

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

Schema coverage is 100%, so the two parameters are fully documented in the schema, including the enum of preset IDs and the list_all flag. The description adds the useful framing that any format preset is supported, which is slightly better than the baseline 3, but it does not explain preset selection trade-offs.

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?

States a concrete verb ('Return') and enumerates the exact spec categories produced: dimensions, safe margins, bleed, grid columns, and typography. That is well beyond a restatement of the name, though it never contrasts itself with any sibling, which is why it lands at 4 rather than 5.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer you call this when you need production specs for a given Canva format. There is no explicit when-to-use or when-not statement, and no pointer to an alternative tool for adjacent needs.

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