Skip to main content
Glama

export_to_svg

Convert Excalidraw drawings to SVG format for scalable vector graphics that maintain quality at any size.

Instructions

Export an Excalidraw drawing to SVG

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The core handler function that executes the export_to_svg tool logic: validates ID, fetches drawing, generates placeholder SVG, handles errors.
    export async function exportToSvg(id: string): Promise<string> {
      // Validate the ID for security
      validateFileId(id);
    
      try {
        // Get the drawing
        const drawing = await getDrawing(id);
    
        // Return the SVG content
        // Note: In a real implementation, we would use the Excalidraw API to convert the drawing to SVG
        // For now, we'll just return a placeholder
        return `<svg>
          <text x="10" y="20">Drawing: ${drawing.name}</text>
          <text x="10" y="40">This is a placeholder for the SVG export.</text>
        </svg>`;
      } catch (error) {
        if (error instanceof ExcalidrawResourceNotFoundError) {
          throw error;
        }
        throw new Error(
          sanitizeErrorMessage(error, "Failed to export drawing to SVG")
        );
      }
  • Zod schema for input validation of the export_to_svg tool, requiring a non-empty string 'id'.
    export const ExportToSvgSchema = z.object({
      id: z.string().min(1),
    });
  • src/index.ts:90-94 (registration)
    Tool registration entry in the listTools handler, defining name, description, and input schema for export_to_svg.
    {
      name: "export_to_svg",
      description: "Export an Excalidraw drawing to SVG",
      inputSchema: zodToJsonSchema(exportOps.ExportToSvgSchema),
    },
  • Dispatch logic in the CallToolRequestSchema handler that parses arguments, calls the exportToSvg function, and formats the response.
    case "export_to_svg": {
      const args = exportOps.ExportToSvgSchema.parse(
        request.params.arguments
      );
      const result = await exportOps.exportToSvg(args.id);
      return {
        content: [{ type: "text", text: result }],
      };
    }
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 of behavioral disclosure. It states the action ('Export') but does not describe what this entails—e.g., whether it requires specific permissions, if it modifies the original drawing, what happens on failure, or any rate limits. This leaves significant gaps in understanding the tool's behavior.

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 directly states the tool's function without unnecessary words. It is front-loaded and appropriately sized for its purpose, with zero waste.

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?

Given the complexity (a mutation-like export operation), lack of annotations, no output schema, and low parameter coverage, the description is incomplete. It does not address behavioral aspects, parameter details, or output expectations, making it inadequate for the agent to fully understand how to use the tool correctly.

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 ('id') with 0% description coverage, meaning the schema provides no semantic information. The description does not add any meaning about the parameter, such as what 'id' refers to (e.g., a drawing identifier) or its format, failing 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 ('Export') and resource ('an Excalidraw drawing to SVG'), making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'export_to_json' or 'export_to_png', which have similar export functions but different formats, so it lacks sibling differentiation.

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 such as 'export_to_json' or 'export_to_png'. It does not mention any context, prerequisites, or exclusions for usage, leaving the agent to infer based on tool names alone.

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/andreswebs-public-images/excalidraw-mcp'

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