mcp-canva

by bryankwandou

Overview Schema Source Related Servers Discussions Admin

Python

Local

desktop_open_url

Open a URL in the default browser to launch Canva or CapCut web editors from an MCP workflow.

Instructions

Open a URL in the default browser on this computer (e.g. a Canva or CapCut web editor).

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>"
    },
    "name": "desktop_open_url"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 16, 2026

TDQS

A3.6/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. It does disclose the key behavioral trait — this has a host-side side effect, launching the OS default browser — but says nothing about whether the call blocks, whether it requires the browser to be installed/available, or how failures (no default browser, malformed URL) surface.

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?

One front-loaded sentence with the action first and the clarifying scope second; 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?

For a one-parameter, single-side-effect tool with an output schema present, the description covers what an agent needs to decide and invoke. Only the blocking/return behavior is left implicit, which is a minor gap.

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

Parameters3/5

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

Schema coverage is 0% for the single `url` parameter, so the schema adds nothing beyond its type. The description partially compensates by giving illustrative URL targets (Canva/CapCut web editors), but adds no format, scheme, or validation guidance.

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?

Specific verb+resource ("Open a URL") plus the destination context ("in the default browser on this computer"), which separates it from browser-based siblings like canva_open_editor or studio_open. It doesn't explicitly name which sibling to prefer, so it stops short of a 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?

The parenthetical "e.g. a Canva or CapCut web editor" implies the intended scenario (launching a web editor in a local browser), but there is no explicit when-to-use versus canva_open_editor/canva_open_desktop/studio_open, and no exclusions or prerequisites.

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