Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Bid Board Project

create_bid_board_project

Create a new Bid Board project in Procore by providing company, name, and status. Returns the created object on success.

Instructions

Create Bid Board project. Use this to create a new Bid Board records in Procore. Creates a new Bid Board records and returns the created object on success (HTTP 201). Required parameters: company_id, name, status. Procore API (v2.0): Preconstruction > Bid Board. Endpoint: POST /rest/v2.0/companies/{company_id}/estimating/bid_board_projects

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique company identifier associated with the Procore User Account.
nameYesJSON request body field — the name of the Bid Board project.
descriptionNoJSON request body field — the description of the Bid Board project.
due_dateNoJSON request body field — the due date of the Bid Board project.
statusYesJSON request body field — the current status of the project.
use_metric_unitsNoJSON request body field — indicates whether the Bid Board project uses metric units.
use_tax_from_costNoJSON request body field — indicates whether the Bid Board project uses tax calculations based on cost.
individual_labor_ratesNoJSON request body field — indicates whether the Bid Board project uses individual labor rates.
project_numberNoJSON request body field — the Bid Board project number.
square_footageNoJSON request body field — the square footage of the Bid Board project.
addressNoJSON request body field — the address associated with the Bid Board project.
is_templateNoJSON request body field — indicates whether the Bid Board project is a template.
use_unit_labor_costNoJSON request body field — indicates whether the Bid Board project uses unit labor cost.
wbs_validation_enabledNoJSON request body field — indicates whether WBS validation is enabled for the Bid Board project.
disable_ea_parts_roundingNoJSON request body field — indicates whether EA parts rounding is disabled for the Bid Board project.
Behavior3/5

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

Annotations already indicate this is a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds that it returns the created object with HTTP 201, but does not disclose additional behavioral traits like authorization needs or side effects beyond what annotations provide.

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 short, front-loaded with the core action, and includes necessary information (purpose, required params, API location) without unnecessary words. Every 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?

Given the tool has 15 parameters, no output schema, and nested objects, the description provides the basic context (endpoint, required params, return status) but lacks details about the return structure, error handling, or permission requirements. It is adequate but not fully complete.

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 all parameters are well-documented in the schema. The description mentions required parameters but does not add new semantic meaning beyond what the schema already provides.

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 tool creates a Bid Board project, uses specific verbs and resources ("Create Bid Board project"), and distinguishes from sibling tools like clone, delete, update, and list by focusing on creation. It also references the API endpoint and version.

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 explicitly says "Use this to create a new Bid Board records" and lists required parameters, providing clear context for usage. However, it does not explicitly state when not to use it or mention alternatives, though the sibling tools imply when to use others.

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