mcp-canva

Overview Schema Source Related Servers Discussions Admin

canva_import_url

Import a file from a public URL as a new editable Canva design. Supply the URL and title to create a design you can edit.

Instructions

Import a file from a public URL as a new editable Canva design.

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": {
      "url": "<url>",
      "title": "<title>"
    },
    "name": "canva_import_url"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes
`title`	Yes
`mime_type`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 16, 2026

TDQS

C2.9/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 behavioral burden. It adds only the 'public URL' constraint and the fact that it creates a new editable design; it says nothing about authentication, supported formats, size limits, failure behavior, or whether an existing design is affected. For an unannotated mutation tool this is a significant gap.

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?

A single, well-formed sentence that front-loads the action and resource with no filler. It is appropriately sized, though brevity here is partly the result of under-specification rather than disciplined editing.

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?

Given a mutation tool with no annotations, no output schema, and three parameters at 0% schema coverage, the description is too thin. It omits permissions, format/limit constraints, and any indication of what a successful import returns or how errors surface.

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% for all three parameters, so the schema provides no meaning. The description only indirectly clarifies 'url' as needing to be public; it says nothing about 'title' or the optional 'mime_type', leaving two of three parameters completely 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 states a specific verb (import) and resource (a file from a public URL) and gives the outcome (a new editable Canva design). It implicitly distinguishes itself from the sibling canva_import_file by specifying 'public URL', but it never names that sibling explicitly.

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: 'public URL' hints that this is the URL-based import path versus a local-file sibling, but there is no explicit when-to-use/when-not-to-use guidance and no alternative is named. An agent must infer the selection criteria.

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