Skip to main content
Glama
TylerIlunga

Procore MCP Server

create_bid_board_project_v2_0

Create a new bid board project in Procore for preconstruction estimating and bid management, enabling contractors to organize bids, track status, and manage project details.

Instructions

Create Bid Board project. [Preconstruction/Bid Board] POST /rest/v2.0/companies/{company_id}/estimating/bid_board_projects

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesUnique company identifier associated with the Procore User Account.
nameYesThe name of the Bid Board project.
descriptionNoThe description of the Bid Board project.
due_dateNoThe due date of the Bid Board project.
statusYesThe current status of the project.
use_metric_unitsNoIndicates whether the Bid Board project uses metric units.
use_tax_from_costNoIndicates whether the Bid Board project uses tax calculations based on cost.
individual_labor_ratesNoIndicates whether the Bid Board project uses individual labor rates.
project_numberNoThe Bid Board project number.
square_footageNoThe square footage of the Bid Board project.
addressNoThe address associated with the Bid Board project.
is_templateNoIndicates whether the Bid Board project is a template.
use_unit_labor_costNoIndicates whether the Bid Board project uses unit labor cost.
wbs_validation_enabledNoIndicates whether WBS validation is enabled for the Bid Board project.
disable_ea_parts_roundingNoIndicates whether EA parts rounding is disabled for the Bid Board project.
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Create' (a write operation) but doesn't disclose behavioral traits like required permissions, whether it's idempotent, rate limits, or what happens on success/failure. The API endpoint hint ('POST') implies mutation, but no safety or side-effect details are given. For a creation tool with zero annotation coverage, this is inadequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief and front-loaded with the core action. The API endpoint detail is extraneous for an AI agent but doesn't add significant bloat. It's efficiently sized, though could be more structured (e.g., separating purpose from technical details).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (15 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the purpose of a 'Bid Board project' in the system, what happens after creation, or any error conditions. For a creation tool with many parameters and no structured safety hints, more context is needed to guide the agent effectively.

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 the schema fully documents all 15 parameters. The description adds no parameter-specific information beyond what's in the schema. According to rules, baseline is 3 when schema does the heavy lifting, even with no param info in description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create Bid Board project' restates the tool name and title (which is null, so it's just the name). It adds minimal context with '[Preconstruction/Bid Board]' and the API endpoint, but doesn't specify what a 'Bid Board project' is or what creation entails beyond the obvious verb. It's vague and lacks differentiation from sibling tools like 'create_project' or 'create_bid_package'.

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

Usage Guidelines1/5

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

No guidance on when to use this tool versus alternatives. Sibling tools include many other creation tools (e.g., 'create_project', 'create_bid_package'), but the description doesn't mention prerequisites, context, or comparisons. It's completely silent on usage scenarios.

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