Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete BIM Plan

delete_bim_plan
DestructiveIdempotent

Permanently delete a BIM Plan and its associated records from Procore using the plan ID and project ID. This action cannot be undone.

Instructions

Delete a BIM Plan from the system. Use this to permanently delete the specified BIM records. This cannot be undone. Permanently removes the specified BIM records. This action cannot be undone. Required parameters: id, project_id. Procore API: Preconstruction > BIM. Endpoint: DELETE /rest/v1.0/bim_plans/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the BIM resource
project_idYesQuery string parameter — unique identifier for the project.
Behavior3/5

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

Annotations already provide destructiveHint=true and idempotentHint=true. The description adds 'This cannot be undone' and 'Permanently removes', reinforcing the destructive nature. It also includes the API endpoint and required parameters, but lacks details on cascading effects or error handling.

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?

The description is relatively concise, front-loading the core action. However, it contains redundant phrasing ('Permanently removes the specified BIM records' repeats the earlier 'permanently delete' and 'This cannot be undone'). Could be slightly tighter but overall good.

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

Completeness4/5

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

For a delete tool with no output schema, the description covers purpose, permanence, required parameters, and API info. Annotations handle behavioral traits. Slightly missing details on success/error responses, but adequate for an agent to use 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?

Input schema coverage is 100% with clear descriptions for both required parameters. The description merely restates that these parameters are required, adding no new meaning beyond the schema. Baseline score of 3 is appropriate as schema does the heavy lifting.

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?

Description clearly states 'Delete a BIM Plan from the system' with a specific verb and resource. The title matches exactly, and among siblings, the tool is distinct as it performs a permanent deletion. The repetition of 'permanently' reinforces the action.

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

Usage Guidelines3/5

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

The description emphasizes permanent deletion and that it cannot be undone, implying use only when final. However, it does not explicitly state when not to use it or provide alternatives (e.g., deactivation). No contrast with sibling tools like update_bim_plan.

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/TylerIlunga/procore-mcp-server'

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