Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create A Batch Of BIM Levels

create_a_batch_of_bim_levels

Create a batch of BIM levels in Procore for a project by submitting an array of BIM Level payloads. Returns the created batch with its new ID.

Instructions

Creates a new batch in Procore. Creates the batch and returns it with its new id (HTTP 201); calling it again creates another record. 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: project_id, bim_levels. Procore API: Preconstruction > BIM. Endpoint: POST /rest/v1.0/bim_levels/batch

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoJSON request body field — specify response schema view
bim_levelsYesJSON request body field — an array of BIM Level payloads
project_idYesJSON request body field — unique identifier for the project.
Behavior4/5

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

The description goes beyond the annotations by detailing the HTTP 201 response with the new id, explicating non-idempotency ('calling it again creates another record'), and listing common error statuses (401, 403, 404). This adds useful behavioral context without contradicting 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 compact and information-dense, with each sentence serving a purpose: operation, behavior, error handling, requirements, and API location. No redundant phrases.

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?

The description provides sufficient context for a write operation, including endpoint, required parameters, response status, and error scenarios. However, it doesn't elaborate on the structure of each BIM Level payload in the array, which is a minor gap given the schema's empty items definition.

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?

Schema coverage is 100%, so the description need not add parameter details. It does restate required parameters but adds no new semantics beyond what the schema already says (project_id, bim_levels). The view parameter is already fully described in the schema enum.

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 identifies the action as creating a batch and the resource as BIM levels, with specific context (Procore, endpoint). It also notes the non-idempotent behavior and HTTP 201 response, effectively distinguishing it from a single-create operation.

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

Usage Guidelines2/5

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

The description does not explicitly state when to use this batch tool versus the single create_bim_level tool, nor does it mention any exclusions or prerequisites. Usage is only implied by the word 'batch' and the required parameters.

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