Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Bid Board Project

update_bid_board_project

Update an existing Bid Board project by modifying only the supplied fields. Returns the updated project object.

Instructions

Update Bid Board project. Use this to update an existing Bid Board records (only the supplied fields are changed). Updates the specified Bid Board records and returns the modified object on success. Required parameters: bid_board_project_id, company_id. Procore API (v2.0): Preconstruction > Bid Board. Endpoint: PATCH /rest/v2.0/companies/{company_id}/estimating/bid_board_projects/{bid_board_project_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bid_board_project_idYesURL path parameter — unique BidBoard project identifier
company_idYesURL path parameter — unique company identifier associated with the Procore User Account.
nameNoJSON 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.
statusNoJSON request body field — the current status of the Bid Board project.
archivedNoJSON request body field — indicates whether the Bid Board project is archived.
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.
pricing_lockedNoJSON request body field — indicates whether the Bid Board project pricing is locked.
deletedNoJSON request body field — indicates whether the Bid Board project is deleted.
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.
Behavior4/5

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

Annotations indicate non-readOnly, non-destructive, non-idempotent, open world. The description adds that it updates records and returns the modified object on success, and that only supplied fields are changed. This provides behavioral context beyond the annotations without contradiction.

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 concise with 5 front-loaded sentences. Each sentence serves a purpose: stating the operation, usage guidance, behavior, required parameters, and API source. There is no extraneous information.

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?

Given the high number of parameters (19) and no output schema, the description adequately covers the key behavior: partial update returning the modified object. It also mentions the API endpoint. It is complete for an update tool with rich schema coverage, though it could hint at error handling.

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 description does not need to add parameter details. It only lists required parameters, but the schema already describes each parameter thoroughly. Thus a baseline score of 3 is appropriate.

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 'Update Bid Board project' with the verb 'update' and resource 'Bid Board project'. It distinguishes from siblings like clone_bid_board_project and update_bid_board_project_custom_field by specifying that only supplied fields are changed, indicating a partial update (PATCH).

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 instructs 'Use this to update an existing Bid Board records (only the supplied fields are changed)' and lists required parameters. While it implies when to use (partial update), it does not explicitly mention when not to use or provide alternatives like clone or custom field update, so a 4 is appropriate.

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