Skip to main content
Glama

update_drawing

Modify existing Excalidraw diagrams by providing new content to update specific drawings identified by their unique ID.

Instructions

Update an Excalidraw drawing by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
contentYes

Implementation Reference

  • Core handler function that updates the drawing content in the JSON file and updates the metadata with new timestamp.
    export async function updateDrawing(id: string, content: string): Promise<{ id: string, name: string }> {
      await ensureStorageDir();
      
      // Get the drawing file path
      const filePath = path.join(STORAGE_DIR, `${id}.json`);
      const metadataPath = path.join(STORAGE_DIR, `${id}.meta.json`);
      
      try {
        // Check if the drawing exists
        await fs.access(filePath);
        
        // Read the metadata
        const metadataStr = await fs.readFile(metadataPath, 'utf-8');
        const metadata = JSON.parse(metadataStr);
        
        // Update the drawing content
        await fs.writeFile(filePath, content, 'utf-8');
        
        // Update the metadata
        metadata.updatedAt = new Date().toISOString();
        await fs.writeFile(metadataPath, JSON.stringify(metadata, null, 2), 'utf-8');
        
        return { id, name: metadata.name };
      } catch (error) {
        throw new ExcalidrawResourceNotFoundError(`Drawing with ID ${id} not found`);
      }
    }
  • MCP server handler case that parses arguments using the schema and calls the updateDrawing function.
    case "update_drawing": {
      const args = drawings.UpdateDrawingSchema.parse(request.params.arguments);
      const result = await drawings.updateDrawing(args.id, args.content);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
  • Zod schema defining the input parameters: id (string) and content (string).
    export const UpdateDrawingSchema = z.object({
      id: z.string().min(1),
      content: z.string().min(1),
    });
  • index.ts:73-76 (registration)
    Tool registration in the ListTools response, including name, description, and input schema.
      name: "update_drawing",
      description: "Update an Excalidraw drawing by ID",
      inputSchema: zodToJsonSchema(drawings.UpdateDrawingSchema),
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states 'Update' which implies mutation, but doesn't specify permissions required, whether changes are reversible, rate limits, or what happens on success/failure. This is inadequate for a mutation tool with zero annotation coverage.

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?

The description is a single, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for a simple update operation and front-loads the essential information.

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 mutation tool with no annotations, no output schema, and 2 undocumented parameters, the description is insufficient. It doesn't explain what 'content' should contain, what happens after update, or error conditions. The context signals indicate significant gaps that aren't addressed.

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%, so the description must compensate. It mentions 'by ID' which hints at the 'id' parameter, but doesn't explain what 'content' represents or its format. With 2 undocumented parameters, the description adds minimal value beyond what's implied by the tool name.

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 action ('Update') and resource ('Excalidraw drawing by ID'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its siblings like 'create_drawing' or 'get_drawing' beyond the basic verb difference, which prevents a perfect score.

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 like 'create_drawing' for new drawings or 'get_drawing' for retrieval. There's no mention of prerequisites (e.g., needing an existing drawing ID) or exclusions, leaving usage context unclear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/i-tozer/excalidraw-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server