Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update BIM Level

update_bim_level
Idempotent

Update an existing BIM level by sending only the fields to change. Requires the BIM level ID, project ID, and the updated BIM level object.

Instructions

Update a BIM Level item. Send only the fields you intend to change; omitted fields keep their current values. id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified BIM level on success. 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, bim_level. Procore API: Preconstruction > BIM. Endpoint: PATCH /rest/v1.0/bim_levels/{id}

Input Schema

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

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

Discloses partial update behavior, success return value, and failure modes with specific HTTP status codes (401/403/404), adding substantial context beyond the annotations. Also notes that id must reference an existing parent record, clarifying an important constraint.

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?

A single, well-structured paragraph that leads with the purpose and then packs in update semantics, prerequisites, return behavior, error examples, and API context. Every sentence adds value; the only minor redundancy is restating required parameters already in the schema.

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 3-parameter mutation with a nested object and no output schema, the description covers the essential workflow, success/failure behavior, and error handling. Including the endpoint and Procore API section makes it self-contained for an agent to invoke correctly.

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 covers all three parameters, so the baseline is 3. The description adds meaning by explaining that id must be resolved with a list tool and that the bim_level object should contain only fields to change. This goes beyond the schema's basic identifiers.

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?

Clearly states 'Update a BIM Level item' with a specific verb and resource. Distinguishes itself from sibling create/list/show/delete tools by focusing on the update action and partial-update semantics.

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?

Provides a clear prerequisite: 'id must identify an existing parent record — resolve it with the matching list tool first.' This guides when to use the tool and which prior action to take, though it does not explicitly list exclusions or alternatives for creation/deletion.

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