excalidraw-editor-mcp

by creativedswork

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Save Excalidraw canvas copy

save_canvas_copy

Avoid overwriting the original by saving the current draft as a new canvas in the same project.

Instructions

Saves the bound draft as a new canvas in the same project.

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": {
      "canvasPath": "<canvasPath>",
      "newCanvasPath": "<newCanvasPath>",
      "mutationId": "<mutationId>",
      "document": "<document>"
    },
    "name": "save_canvas_copy"
  }
}

Input Schema

Name	Required	Description
`document`	Yes
`canvasPath`	Yes	Full workspace-relative canvas path under projectPath, for example designs/m3/main.excalidraw. Never pass only main.excalidraw.
`mutationId`	Yes
`newCanvasPath`	Yes	Full workspace-relative canvas path under projectPath, for example designs/m3/main.excalidraw. Never pass only main.excalidraw.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Sep 7, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description must carry behavioral context, but it only says 'saves' and 'new canvas in the same project.' It does not disclose side effects, whether an existing newCanvasPath is overwritten, idempotency behavior, or what happens to the original draft.

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?

The description is a single front-loaded sentence with no unnecessary words. It is concise, though its brevity comes at the cost of behavioral detail.

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 4-parameter tool with a nested document object, no output schema, and no annotations, one sentence leaves critical gaps: what document should contain, the role of mutationId, and the expected result. The same-project and new-canvas constraints are useful but insufficient.

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 coverage is only 50%, and the description does not compensate. It loosely maps 'bound draft' to the document parameter and 'new canvas' to newCanvasPath, but mutationId and document remain effectively undocumented in the description, so an agent gets little additional meaning.

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 action and outcome: the bound draft is saved as a new canvas in the same project. This distinguishes it from applying changes to an existing canvas or duplicating an existing canvas, though 'bound draft' is not fully defined.

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 guidance is given about when to use this tool versus alternatives such as duplicate_canvas, push_canvas, or apply_canvas_changes. The phrase 'as a new canvas' implies a save-as-copy use case, but no exclusions or selection criteria are provided.

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