Skip to main content
Glama
elkhouryrafik-boop

revit-mcp-hardened

delete_elements

Delete Revit model elements by ID. Use dry_run to preview deletions before applying. Cascades removals and reports failures for protected elements.

Instructions

Delete elements from the model, by element id.

Destructive. Prefer calling once with dry_run=True first: that returns exactly what would be removed without touching the model, which is worth doing whenever the ids came from a filter rather than from an explicit user selection.

Deleting one element can cascade - removing a wall also removes the doors and windows hosted in it - so deleted_count can exceed the number of ids supplied. The dry run cannot predict cascades.

Does NOT accept a category or a filter, only explicit ids: use reset_model for category-wide clearing, which has its own confirmation guards.

Elements that are pinned, owned by another user in a workshared model, or structurally required (such as the last level) cannot be deleted and are reported as failures.

Args: element_ids: Element ids to delete. Must be non-empty. dry_run: When True, report what would be deleted and change nothing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNo
element_idsYes
Behavior5/5

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

With no annotations, the description fully carries behavioral disclosure. It details destructive nature, cascading deletions (deleted_count can exceed ids), dry run limitations (cannot predict cascades), and specific failure cases (pinned, owned by another user, structurally required).

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 front-loads the core purpose in the first sentence, then layers usage guidance, behavioral caveats, and parameter clarification. Every sentence adds value, and the structure guides the agent from safe usage to edge cases.

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?

The description is exceptionally complete for a destructive tool. It covers purpose, when to use, alternatives, dry run behavior, cascades, limitations, and parameter semantics, leaving no critical gap—even without an output schema or annotations.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has no descriptions (0% coverage), so the description compensates fully. It explains element_ids must be explicit and non-empty, and dry_run returns what would be deleted without changing anything. The dry_run parameter is clearly tied to the usage guidance.

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?

The description opens with a specific verb and resource: 'Delete elements from the model, by element id.' It also clearly distinguishes from siblings by stating it does NOT accept a category or filter, directing to reset_model for category-wide clearing.

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

Usage Guidelines5/5

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

Explicit guidance is provided: 'Prefer calling once with dry_run=True first' and 'use reset_model for category-wide clearing.' It also clarifies when not to use it (no category/filter) and when dry run is especially advisable (when ids came from a filter).

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/elkhouryrafik-boop/revit-mcp-hardened'

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