Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete BIM File

delete_bim_file
DestructiveIdempotent

Permanently delete a BIM file from Procore when it is not associated with BIM levels, revisions, viewpoints, or coordination issues. Confirm the ID with a list tool before calling.

Instructions

Delete a BIM File from the system. A BIM File can only be deleted if it is not associated with BIM Levels, Revisions, or Viewpoints or Coordination Issues. Confirm the target id with the matching show or list tool before calling. id must identify an existing parent record — resolve it with the matching list tool first. Permanently removes the BIM file. This cannot be undone, and a repeat call returns 404. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: id, project_id. Procore API: Preconstruction > BIM. Endpoint: DELETE /rest/v1.0/bim_files/{id}

Input Schema

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

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

Beyond annotations, it discloses that deletion is permanent and cannot be undone, a repeat call returns 404, and failures return error payloads with common HTTP status codes (401, 403, 404). This gives the agent a clear picture of side effects and 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.

Conciseness5/5

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

The description is thorough yet organized, with each sentence providing distinct value: action, preconditions, resolution guidance, permanence, error behavior, required params, and API reference. It is front-loaded and not redundant.

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?

For a delete operation with no output schema, the description covers all critical context: prerequisites, irreversibility, error handling, and required parameters. It is complete enough for an agent to safely invoke the tool.

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

Parameters4/5

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

The schema already documents both params with 100% coverage. The description adds meaning by explaining that id must identify an existing parent record and should be resolved via the matching list tool, providing context beyond the basic schema descriptions.

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 'Delete a BIM File from the system,' clearly stating the action and resource. It distinguishes itself from sibling tools like show_bim_file and create_bim_file by focusing on deletion and explicitly mentioning the DELETE endpoint.

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?

It provides explicit guidance on when to use: only when the BIM file is not associated with BIM Levels, Revisions, Viewpoints, or Coordination Issues. It also instructs to confirm the target id with the matching show or list tool before calling, effectively naming alternatives for verification.

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