excalidraw-editor-mcp

Overview Schema Source Related Servers Discussions Admin

Rename Excalidraw canvas

rename_canvas

Rename a canvas file within an Excalidraw project by providing project path, old canvas path, and new canvas path. Updates the diagram location while keeping it in the same managed project.

Instructions

Renames a canvas inside the same managed 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": {
      "projectPath": "<projectPath>",
      "canvasPath": "<canvasPath>",
      "newCanvasPath": "<newCanvasPath>",
      "baseRevision": "<baseRevision>",
      "mutationId": "<mutationId>"
    },
    "name": "rename_canvas"
  }
}

Input Schema

Name	Required	Description
`canvasPath`	Yes	Full workspace-relative canvas path under projectPath, for example designs/m3/main.excalidraw. Never pass only main.excalidraw.
`mutationId`	Yes
`projectPath`	Yes	Full workspace-relative project path, for example designs/m3.
`baseRevision`	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 provided, the description carries the full burden of behavioral disclosure. 'Renames' implies a mutating operation, but the description does not explain whether the operation is reversible, what happens if the target path already exists, whether the old path is removed, or why baseRevision and mutationId are required. This is a significant gap for a mutation 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?

The description is a single efficient sentence with no filler words. It front-loads the core operation and scope. The brevity, however, sacrifices useful detail, which is a tradeoff, but conciseness itself is handled well.

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 tool with 5 required parameters, no output schema, and no annotations, the description is notably incomplete. It omits the semantics of mutationId and baseRevision, preconditions, side effects, and error conditions. An agent would struggle to call this tool correctly without external knowledge or schema inspection.

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?

The description adds no parameter-level meaning beyond the input schema. Schema coverage is 60%: three parameters (canvasPath, projectPath, newCanvasPath) are well-documented, but mutationId and baseRevision have no schema descriptions and the description does not compensate by explaining their purpose (e.g., conflict resolution and idempotency).

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 clearly states the verb 'Renames' and the resource 'canvas', and adds a scoping constraint 'inside the same managed project.' It is distinguishable from rename_project, though it does not explicitly differentiate from similar canvas operations like replace_canvas or duplicate_canvas.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., the canvas must already exist), when not to use it, or which sibling tools are better suited for similar operations. The 'same managed project' clause hints at scope but is not enough to constitute usage guidance.

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