Skip to main content
Glama
Sign In
Archicad MCP Connector

Archicad MCP Connector

by davidharutyunyan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Delete elements

delete_elements
Destructive

Delete any elements from an Archicad project by GUID in one undo step. Removes dependent items like doors, dimensions, and sub-elements automatically and reports everything deleted.

Instructions

Deletes elements of ANY type (one undo step: undo restores them). Dependent elements are removed by Archicad too and are reported: windows/doors of deleted walls, associative dimensions and labels, etc. -> alsoDeleted: [{guid, type}], subElementsDeleted (curtain wall / stair / railing parts). Only delete elements you created or were asked to delete. Group GUIDs delete the whole group. Returns {results: [{guid, deleted: true} | {guid, error}], deletedCount, alsoDeleted?, subElementsDeleted?, warnings?}.

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": {
      "elements": "<elements>"
    },
    "name": "delete_elements"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementsYesElements to edit: GUID strings (or {guid}) of any element type, e.g. from get_element_details / element search tools. A group GUID stands for all elements of that group.
includeGroupMembersNoDefault false: ONLY the listed elements are affected even when they belong to groups (Suspend Groups is switched on for the duration of the call and restored afterwards). true: all members of their (top-level) groups are affected as well.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description goes well beyond them: one undo step restores, dependent elements (openings of walls, associative dimensions/labels, curtain wall/stair/railing sub-elements) are cascade-deleted by Archicad, and group GUIDs delete entire groups. This is exactly the extra destructive-behavior context an agent needs.

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?

Front-loads the core action and undo guarantee, then packs cascades, group semantics, and the return shape into a dense block. Slightly run-on with the inline return-type listing, but every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description enumerates the return shape (results with deleted/error, deletedCount, alsoDeleted, subElementsDeleted, warnings) and explains cascade and group behavior. An agent has everything needed to invoke and interpret this destructive tool correctly.

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 100%, so the schema already documents both `elements` (GUID strings or {guid}, group GUID = whole group) and `includeGroupMembers`. The description's group-GUID note largely repeats the schema, and it adds no syntax detail beyond it; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource and immediately scopes it ("Deletes elements of ANY type"), which distinguishes it from the many typed deletion siblings like delete_stories, delete_drawings, delete_attributes. The group-GUID behavior further pins down the tool's coverage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a real usage constraint ("Only delete elements you created or were asked to delete") and notes the one-undo-step reversibility, which informs risk. It does not name alternatives (e.g. ungroup/undo) or state when not to use it beyond the caution, so it stops short of a 5.

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

Deploy Server

Other Tools