Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update A Purchase Order

update_a_purchase_order
Idempotent

Update purchase order header fields like title, delivery date, notes, or status. Omitted fields keep current values; returns the updated purchase order.

Instructions

Updates header fields on a purchase order document such as title, delivery date, notes, and status. Use status transitions to move the purchase order through its workflow states. Send only the fields you intend to change; omitted fields keep their current values. company_id and project_id default to the values 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 purchase order 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: id, company_id, project_id. Procore API (v2.0): Resource Management > Materials Management. Endpoint: PATCH /rest/v2.0/companies/{company_id}/projects/{project_id}/materials_mgmt/purchase_orders/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Materials Management resource
nameNoJSON request body field — name of the document header.
notesNoJSON request body field — notes associated with the document header.
vendorNoJSON request body field — the vendor for this Materials Management operation
company_idYesURL path parameter — the company identifier
project_idYesURL path parameter — the project identifier
descriptionNoJSON request body field — description of the document header.
properties_to_addNoJSON request body field — collection of resource parameters to add to the document header.
properties_to_deleteNoJSON request body field — collection of resource parameters to delete from the document header.
properties_to_updateNoJSON request body field — collection of resource parameters to update in the document header.
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description discloses partial-update semantics, default values for company_id/project_id when omitted, return value on success, and common failure modes with HTTP statuses (401, 403, 404). It also introduces the workflow-state transition behavior, which is not visible in the schema.

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 (nearly 10 sentences) but front-loaded with the core purpose and packed with necessary detail. Every sentence provides distinct information—scope, status transitions, patch semantics, defaults, prerequisites, return value, errors, and endpoint—so it earns its place, though it could be tightened.

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?

For a mutation tool with 10 parameters and no output schema, the description thoroughly covers the key aspects: what fields are updated, how to handle partial updates, how to obtain the id, default behavior, success/failure responses, and the exact endpoint. The schema documents the parameter names and types, so the description completes the operational picture.

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%, so the baseline is 3. The description adds value by explaining the partial-update behavior (omitted fields keep current values), the role of id (must reference an existing parent record), and the fallback behavior for company_id/project_id via procore_set_config. This meaningfully supplements the generic schema descriptions.

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 uses a specific verb phrase ('Updates header fields') with a concrete resource ('purchase order document') and lists example fields (title, delivery date, notes, status). This clearly distinguishes it from sibling list/create/delete operations and narrower tools like line-item updates.

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

Usage Guidelines5/5

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

It explicitly states when to use the tool (updating header fields, moving through workflow states via status transitions) and provides a prerequisite (resolve id with the matching list tool). It also gives partial-update guidance ('Send only the fields you intend to change') and explains the default behavior for company_id/project_id, which is actionable usage guidance.

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