Skip to main content
Glama
Abdullah007bajwa

Excalidraw MCP Server

delete_element

Remove specific elements from Excalidraw diagrams by ID to clean up or edit visual content.

Instructions

Delete an Excalidraw element

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The switch case handler in the CallToolRequestSchema that executes the delete_element tool: parses the ID using Zod schema, verifies existence in the elements Map, deletes the element, and returns a JSON response indicating success.
    case 'delete_element': {
      const params = ElementIdSchema.parse(args);
      const { id } = params;
      
      if (!elements.has(id)) throw new Error(`Element with ID ${id} not found`);
      
      elements.delete(id);
      
      return {
        content: [{ type: 'text', text: JSON.stringify({ id, deleted: true }, null, 2) }]
      };
    }
  • src/index.js:145-154 (registration)
    Registration of the delete_element tool in the MCP server capabilities, including its description and input schema.
    delete_element: {
      description: 'Delete an Excalidraw element',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string' }
        },
        required: ['id']
      }
    },
  • Zod schema (ElementIdSchema) used to validate and parse the input arguments (id) for the delete_element handler.
    const ElementIdSchema = z.object({
      id: z.string()
    });
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 burden. It states the action ('Delete') but lacks critical behavioral details: whether deletion is permanent or reversible, if it requires specific permissions, what happens to related elements (e.g., in groups), or error conditions (e.g., invalid ID). This is inadequate for a destructive operation 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 with zero wasted words. It's front-loaded with the core action and resource, making it immediately understandable without unnecessary elaboration.

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 destructive tool with no annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't address behavioral risks, parameter semantics, or usage context, leaving significant gaps that could lead to incorrect agent decisions.

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 input schema has 1 parameter with 0% description coverage, so the schema provides no semantic context. The description doesn't add any parameter information—it doesn't explain what 'id' represents (e.g., element identifier format), where to obtain it, or validation rules. This fails to compensate for the low schema coverage.

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 ('Delete') and resource ('an Excalidraw element'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'update_element' or 'lock_elements' in terms of when deletion is appropriate versus modification or state changes.

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 doesn't mention prerequisites (e.g., element must exist), exclusions (e.g., cannot delete locked elements), or comparisons to siblings like 'update_element' for modifications or 'query_elements' for checking status before deletion.

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/Abdullah007bajwa/mcp_excalidraw'

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