Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Project Task

update_project_task_company_v2_0

Update an existing Bid Board project task by providing its ID, company ID, and project ID. Modify fields like description, due date, assignment, or completion status.

Instructions

Update project task. 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: task_id, company_id, bid_board_project_id. Procore API (v2.0): Preconstruction > Bid Board. Endpoint: PATCH /rest/v2.0/companies/{company_id}/estimating/bid_board_projects/{bid_board_project_id}/tasks/{task_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesURL path parameter — unique identifier of the task
company_idYesURL path parameter — unique company identifier associated with the Procore User Account.
bid_board_project_idYesURL path parameter — unique BidBoard project identifier
valueNoJSON request body field — the updated description of the task.
due_dateNoJSON request body field — the updated due date of the task.
assigned_to_user_idNoJSON request body field — the updated identifier of the user to whom the task is assigned. For getting assigned_to_user_id look "company users" endpoint.
completedNoJSON request body field — indicates whether the task is completed. This property is only used for updating completion status via patch request.
Behavior3/5

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

Annotations already indicate readOnlyHint=false (write operation). The description adds that it returns the modified object on success, which is useful, but does not discuss side effects, permissions, or idempotency. 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.

Conciseness4/5

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

The description is front-loaded with the purpose. However, the last sentence is verbose, repeating 'Required parameters' and then listing them again along with API endpoint details. Could be more concise.

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 that there is no output schema and the tool has 7 parameters, the description covers the core functionality, required parameters, and expected return. It does not mention error handling or permissions, but for a straightforward update tool this is adequate.

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 lists required parameters but adds no new meaning beyond what the schema provides (e.g., that task_id is a URL path parameter is already in schema).

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 it updates a project task (specific verb+resource) and references 'Bid Board records', distinguishing it from other update tools. The first sentence immediately conveys the action.

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

Usage Guidelines3/5

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

The description lists required parameters and mentions 'only the supplied fields are changed' (partial update), but does not explicitly state when to use this tool versus alternatives like bulk_delete or other update tools. No contrast with sibling tools is provided.

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