Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Commitment Change Order Line Item

create_commitment_change_order_line_item

Add a new line item to a commitment change order, specifying WBS code and costs for procurement tracking in Procore.

Instructions

Creates a line item for a given commitment change order. Use this to create a new Commitments in Procore. Creates a new Commitments and returns the created object on success (HTTP 201). Required parameters: company_id, project_id, commitment_change_order_id, wbs_code_id. Procore API (v2.0): Construction Financials > Commitments. Endpoint: POST /rest/v2.0/companies/{company_id}/projects/{project_id}/commitment_change_orders/{commitment_change_order_id}/line_items

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.
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_idYesJSON request body field — unique identifier of the wbs code
tax_code_idNoJSON request body field — unique identifier of the tax code
Behavior3/5

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

Annotations (readOnlyHint=false, destructiveHint=false) are not contradicted. Description adds that it returns the created object (HTTP 201) and lists the endpoint, but does not disclose side effects, permissions, or error conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is mostly concise but includes a confusing and redundant sentence about creating commitments. It could be streamlined to avoid ambiguity.

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

Completeness2/5

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

The description does not explain prerequisites (e.g., commitment change order must exist), typical usage, or return value structure beyond 'created object'. No output schema exists, so more detail on response would be beneficial.

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?

Input schema has 100% description coverage, so the schema already explains each parameter. The description only repeats required parameters, adding no new semantic meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it creates a line item for a commitment change order and provides the endpoint. However, it confusingly says 'Use this to create a new Commitments in Procore,' which is misleading as it creates a line item, not a commitment.

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

Usage Guidelines2/5

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

The description does not specify when to use this tool versus alternatives like create_commitment_contract_line_item. It mentions required parameters but offers no context on prerequisites or scenarios.

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