Skip to main content
Glama
Abdullah007bajwa

Excalidraw MCP Server

ungroup_elements

Separate grouped elements in Excalidraw diagrams to edit individual components independently.

Instructions

Ungroup a group of elements

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupIdYes

Implementation Reference

  • The main handler logic for the 'ungroup_elements' tool. It validates the input using GroupIdSchema, checks if the group exists in sceneState.groups, retrieves the element IDs, deletes the group, and returns a success response with the details.
    case 'ungroup_elements': {
      const params = GroupIdSchema.parse(args);
      const { groupId } = params;
      
      if (!sceneState.groups.has(groupId)) {
        throw new Error(`Group ${groupId} not found`);
      }
      
      const elementIds = sceneState.groups.get(groupId);
      sceneState.groups.delete(groupId);
      
      const result = { groupId, ungrouped: true, elementIds };
      return {
        content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
      };
    }
  • Zod schema used for input validation of the groupId parameter in the ungroup_elements handler.
    const GroupIdSchema = z.object({
      groupId: z.string()
    });
  • src/index.js:197-206 (registration)
    Tool registration in the MCP server capabilities, including the description and input schema definition.
    ungroup_elements: {
      description: 'Ungroup a group of elements',
      inputSchema: {
        type: 'object',
        properties: {
          groupId: { type: 'string' }
        },
        required: ['groupId']
      }
    },
  • Duplicate schema definition in the ListToolsRequestHandler for consistency.
    name: 'ungroup_elements',
    description: 'Ungroup a group of elements',
    inputSchema: {
      type: 'object',
      properties: {
        groupId: { type: 'string' }
      },
      required: ['groupId']
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action ('ungroup') but doesn't disclose behavioral traits such as whether this is a destructive operation (e.g., does it delete the group or just dissolve it?), permission requirements, side effects on element properties, or error conditions. The description is minimal and lacks critical context 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with a single sentence ('Ungroup a group of elements'), which is front-loaded and wastes no words. It directly states the purpose without unnecessary elaboration, making it efficient for quick understanding.

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 tool's complexity (a mutation operation with no annotations, 1 parameter at 0% coverage, and no output schema), the description is incomplete. It doesn't explain what 'ungroup' entails (e.g., whether elements retain properties, if the group is deleted), provide usage context, or detail parameter meaning. For a tool that likely modifies state, this is insufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 implies a 'groupId' parameter but doesn't explain its semantics (e.g., what format it expects, how to obtain it, or what happens if invalid). The description adds minimal value beyond the schema, resulting in a baseline score due to inadequate parameter explanation.

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 ('ungroup') and target ('a group of elements'), providing a specific verb+resource combination. It distinguishes from siblings like 'group_elements' (opposite operation) and 'delete_element' (different action). However, it doesn't specify what happens to the elements after ungrouping or what 'ungroup' means in this context.

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 provided about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an existing group), exclusions (e.g., what happens if elements aren't grouped), or comparisons to siblings like 'delete_element' (which might remove elements entirely). Usage is implied but not explicitly stated.

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