Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create BIM File

create_bim_file

Create a BIM file in a Procore project to obtain a new ID. Works with authenticated access and reports token, permission, or not-found errors.

Instructions

Create a BIM File in a Project. Creates the BIM file 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_file. Procore API: Preconstruction > BIM. Endpoint: POST /rest/v1.0/bim_files

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bim_fileYesJSON request body field — bIM File Item object. Each BIM File can be uniquely identified by name and UUID.
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 non-read-only, non-idempotent operation. The description adds HTTP 201 success, duplicate creation warning, and specific error codes (401/403/404), which are valuable beyond 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 tightly written, front-loaded with the purpose, and includes only relevant operational details (behavior, errors, required params, endpoint).

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?

For a create tool with no output schema, the description explains the key return value (new id) and error conditions, though it doesn't describe the full response object or detailed input structure for bim_file.

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 covers both parameters with descriptions, so baseline is 3. The description only lists required parameters without adding further meaning about the nested bim_file object structure.

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 action ('Create a BIM File in a Project'), the outcome (returns new id, HTTP 201), and distinguishes from siblings like delete_bim_file/list_bim_files/update_bim_file by specifying the create operation and its unique characteristics.

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 clear context for when to use (creating a BIM file) and notes non-idempotent behavior ('calling it again creates another record'), but doesn't explicitly compare to alternative tools or state when not to use it.

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