Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update BIM File

update_bim_file

Update an existing BIM file record by modifying only the supplied fields. Returns the updated object upon success.

Instructions

Update BIM File. Use this to update an existing BIM records (only the supplied fields are changed). Updates the specified BIM records and returns the modified object on success. Required parameters: id, project_id, bim_file. Procore API: Preconstruction > BIM. Endpoint: PATCH /rest/v1.0/bim_files/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the BIM resource
project_idYesJSON request body field — unique identifier for the project.
bim_fileYesJSON request body field — bIM File Item object
Behavior3/5

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

Annotations already indicate non-readonly, non-destructive, non-idempotent. Description adds that it returns the modified object, but otherwise provides limited behavioral context beyond the annotations.

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 concise, front-loaded with the purpose, and contains no unnecessary words. Each sentence adds value.

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

Completeness3/5

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

No output schema is provided, and the description only vaguely mentions 'returns the modified object on success'. It lacks details on error conditions, partial update behavior, and authentication requirements.

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?

Schema coverage is 100%, but the description adds value by specifying which parameters are URL path vs. JSON body fields, enhancing understanding beyond the schema.

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 clearly states the verb 'Update' and resource 'BIM File', and specifies partial update semantics. It is distinct from siblings like create_bim_file and delete_bim_file.

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?

The description mentions required parameters and provides API endpoint context, but does not explicitly state when to use this vs. alternatives like create_bim_file or delete_bim_file.

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