Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Workflow Bulk Replace Request

update_workflow_bulk_replace_request
Idempotent

Update existing workflow bulk replace requests by sending only changed fields. Validate and queue async operations, including retrying requests that previously contained errors.

Instructions

Updates an existing workflows bulk replace request. This API validates the input, updates the request record in the DB, and creates a new async operation record. The request must be temporary to be updated. The replacement type and original assignee cannot be changed. This API will queue another async operation even if the update does not introduce any changes, effectively "retrying" a request that previously contained errors. Send only the fields you intend to change; omitted fields keep their current values. company_id defaults to the value set by procore_set_config when omitted, and id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified workflow bulk replace request on success. 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: company_id, id. Procore API (v2.0): Core > Workflows. Endpoint: PUT /rest/v2.0/companies/{company_id}/workflows/bulk_replace_requests/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier for the workflow bulk replace request.
toolsNoJSON request body field — array of tool configurations to limit replacement scope (optional)
reasonNoJSON request body field — reason for the replacement
end_dateNoJSON request body field — end date for temporary replacements
company_idYesURL path parameter — unique identifier for the company.
start_dateNoJSON request body field — start date for temporary replacements
project_idsNoJSON request body field — array of project IDs to limit replacement scope (optional)
new_assignee_idsNoJSON request body field — array of IDs for new assignees
modify_project_rolesNoJSON request body field — whether to modify project roles during replacement
new_workflow_manager_idNoJSON request body field — iD of the new workflow manager (optional)
Behavior1/5

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

The description contradicts the idempotentHint=true annotation by stating 'This API will queue another async operation even if the update does not introduce any changes.' This means repeated identical calls create additional async operation records, making the operation non-idempotent in its full side effects. The contradiction overrides otherwise rich behavioral disclosure.

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 long but every sentence carries essential information: purpose, preconditions, constraints, side effects, error handling, and endpoint. It is front-loaded with the main action and well-structured, though it could be slightly trimmed without losing value.

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

Completeness5/5

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

Despite lacking an output schema, the description covers purpose, prerequisites, field immutability, async operation behavior, defaults, id resolution, return value, error statuses, required parameters, and the endpoint. This is thorough for a complex update operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds critical semantics beyond field names: partial update semantics ('Send only the fields you intend to change; omitted fields keep their current values'), company_id defaulting to procore_set_config, and the requirement to resolve id via the list tool. These details help the agent construct correct calls.

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 opens with 'Updates an existing workflows bulk replace request,' a specific verb+resource that clearly distinguishes it from sibling tools like create, show, stop, and download for bulk replace requests. It also adds constraints (must be temporary, cannot change replacement type/original assignee) that further clarify the tool's scope.

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 states when the tool is appropriate (updating an existing temporary request) and includes prerequisites like 'id must identify an existing parent record — resolve it with the matching list tool first.' It also provides partial-update guidance and notes that company_id defaults to config. It does not explicitly name alternative tools, but the context makes selection clear.

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