Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Commitment Change Order Line Item

update_commitment_change_order_line_item

Update a line item in a commitment change order by specifying only the fields to change. Returns the modified commitment line item.

Instructions

Updates a line item for a given commitment change order. Use this to update an existing Commitments (only the supplied fields are changed). Updates the specified Commitments and returns the modified object on success. Required parameters: company_id, project_id, commitment_change_order_id, id. Procore API (v2.0): Construction Financials > Commitments. Endpoint: PATCH /rest/v2.0/companies/{company_id}/projects/{project_id}/commitment_change_orders/{commitment_change_order_id}/line_items/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
project_idYesURL path parameter — unique identifier for the project.
commitment_change_order_idYesURL path parameter — unique identifier for the Commitment Change Order.
idYesURL path parameter — unique identifier of the Commitments resource
prime_line_item_idNoJSON request body field — iD of the prime contract line item associated with this line item
commitment_line_item_idNoJSON request body field — iD of the commitment contract line item associated with this line item
amountNoJSON request body field — amount - this field is nullable on unit quantity SOVs but NOT amount-based SOVs. For line item creates, if this field is omitted on unit quantity SOVs, the amount will be calculated as quantity * ...
descriptionNoJSON request body field — the description for this Commitments operation
quantityNoJSON request body field — quantity - only accepted on unit quantity SOVs
unit_costNoJSON request body field — unit cost - only accepted on unit quantity SOVs
uomNoJSON request body field — unit of measure - only accepted on unit quantity SOVs
wbs_code_idNoJSON request body field — unique identifier of the wbs code
tax_code_idNoJSON request body field — unique identifier of the tax code
Behavior4/5

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

Beyond annotations (which are minimal), the description adds that only supplied fields are changed (partial update) and returns the modified object on success. This provides useful behavioral context.

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 concise, front-loaded with purpose, and includes the API endpoint and required parameters. It is clear without being overly verbose.

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

Completeness3/5

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

Covers purpose, partial update, and return value, but given no output schema and 13 parameters, it lacks details on error handling, constraints, or further behavior. Adequate but not complete.

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 coverage is 100%, so baseline is 3. The description lists required parameters and clarifies partial update, but adds little beyond the already detailed 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 clearly states it updates a line item for a commitment change order, uses specific verbs and resource, and distinguishes from sibling tools like create, delete, and list.

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?

It mentions 'Use this to update an existing Commitments' but provides no explicit guidance on when not to use, alternatives, or prerequisites. The context is implied but not explicit.

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