mcp-canva

by bryankwandou

Overview Schema Source Related Servers Discussions Admin

Python

Local

desktop_hotkey

Press key combinations like Ctrl+Z or Space to trigger desktop actions, enabling Canva design control through MCP.

Instructions

Press a key combination, e.g. ["ctrl","z"] or ["space"].

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": {
      "keys": "<keys>"
    },
    "name": "desktop_hotkey"
  }
}

Input Schema

Name	Required	Description	Default
`keys`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

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 does not state which application or focused window receives the keystrokes, modifier semantics, or timing behavior — significant gaps for an automation tool.

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 tight sentence with no waste, and the examples are front-loaded to illustrate usage immediately. Appropriately sized for a one-parameter tool.

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?

With no annotations, 0% schema description coverage, and a desktop-automation context where focus/target behavior matters, the definition leaves too much unspecified. The output schema existing does relieve it of describing return values, but the operational context is thin.

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 'keys' parameter, so the description must compensate. The inline examples (["ctrl","z"], ["space"]) do convey the array-of-key-string format and modifier ordering, adding real value, but key naming conventions remain undocumented.

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 and resource ('Press a key combination'), which is unambiguous and distinct from click/type/scroll siblings by nature. However, it doesn't explicitly name or contrast itself against any sibling to help routing.

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, prerequisites, or alternative guidance is given. The examples hint at format but not at the condition under which this tool should be chosen over desktop_type or desktop_click.

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