mcp-canva

Overview Schema Source Related Servers Discussions Admin

canva_make_from_template

Generate original, editable designs for Instagram posts, stories, YouTube thumbnails, or presentations from a template and import them into Canva.

Instructions

Generate a full original design (instagram_post | story | youtube_thumbnail | presentation) with separate, editable elements, and import it into Canva as a normal editable design. For presentation, body items become slides ("Judul: detail").

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": {
      "template": "<template>",
      "title": "<title>"
    },
    "name": "canva_make_from_template"
  }
}

Input Schema

Name	Required	Default
`cta`	No
`body`	No
`font`	No	Montserrat
`title`	Yes
`images`	No
`palette`	No	bold
`out_path`	No	~/creative-mcp-designs
`subtitle`	No
`template`	Yes
`import_to_canva`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 16, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does disclose that output is imported into Canva as a normal editable design and that presentation body items become slides. It omits permission/auth requirements, whether an existing design is overwritten, what out_path controls, and any rate-limit or failure behavior, which are meaningful for this operation.

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?

Two compact sentences that front-load the core action and the import side effect. The parenthetical type list and slide rule are useful, though the phrasing is slightly cramped.

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 10-parameter, side-effecting tool with no annotations and no output schema, the description is thin: most parameters, permissions, and the resulting design identity are unexplained, so an agent cannot call it fully correctly from this text alone.

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% across 10 parameters. The description only adds semantics for body in the presentation case and implies template/title usage; cta, font, palette, images, subtitle, out_path, and import_to_canva are entirely undocumented, so the description does not 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?

States a specific verb (generate) and resource (a full original design) and enumerates the supported template types, plus the side effect of importing into Canva. However it does not differentiate itself from close siblings like canva_create_design or canva_autofill, so the agent must infer which to use from context alone.

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?

No when-to-use, when-not-to-use, or alternative guidance is given. The description never mentions canva_autofill, canva_create_design, or canva_create_showcase_template, even though those siblings overlap heavily with generating/importing designs, leaving selection entirely to inference.

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