Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create BIM Plan

create_bim_plan

Create a BIM plan in a Procore project by providing the project ID and BIM plan details. The API creates the plan and returns its new ID.

Instructions

Create a BIM Plan in a Project. Creates the BIM plan 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_plan. Procore API: Preconstruction > BIM. Endpoint: POST /rest/v1.0/bim_plans

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoJSON request body field — specify response schema view
bim_planYesJSON request body field — the bim plan for this BIM operation
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?

Annotations already indicate a mutating, non-idempotent operation. The description adds valuable context beyond annotations: HTTP 201 with new id on success, and common error statuses (401, 403, 404) with their meanings. No contradiction with 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?

Description is front-loaded with the core action, then non-idempotency, error handling, required parameters, and API context. Every sentence contributes necessary information; no filler or redundancy.

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?

Covers purpose, non-idempotency, return behavior, error conditions, and required params. However, it does not explain the expected structure/content of the bim_plan string parameter, which is a notable gap since there is no output schema and the schema description is vague.

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 description coverage is 100%, so baseline is 3. The description only repeats the required parameters (project_id, bim_plan) without adding meaning beyond the schema, especially for bim_plan which remains vaguely described as 'the bim plan for this BIM operation'.

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 explicitly states 'Create a BIM Plan in a Project' with a specific verb and resource. It distinguishes from siblings by noting non-idempotency ('calling it again creates another record'), separating it from update/list/batch operations.

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?

Clear context: this is for creating a single new BIM plan, and the warning about duplicate records on repeat calls guides correct use. It doesn't explicitly mention alternatives like create_a_batch_of_bim_plans, but the non-idempotency warning provides practical usage guidance.

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