Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Prime Contract Line Item

update_prime_contract_line_item_project

Updates a line item on a prime contract by sending only the fields to change. Requires company, project, prime contract, and line item IDs.

Instructions

Updates a line item for a given prime contract. Use this to update an existing Prime Contracts (only the supplied fields are changed). Updates the specified Prime Contracts and returns the modified object on success. Required parameters: company_id, project_id, prime_contract_id, id. Procore API (v2.0): Construction Financials > Prime Contracts. Endpoint: PATCH /rest/v2.0/companies/{company_id}/projects/{project_id}/prime_contracts/{prime_contract_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.
prime_contract_idYesURL path parameter — unique identifier for the Prime Contract.
idYesURL path parameter — unique identifier of the Prime Contracts resource
line_item_group_idNoJSON request body field — iD of the line item group to associate 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 Prime Contracts 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
Behavior3/5

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

Annotations already indicate non-readonly, non-destructive, non-idempotent. The description adds that only supplied fields are updated (PATCH behavior) and lists required parameters. No contradictions, but no additional behavioral traits like error handling or auth needs beyond annotations.

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

Conciseness5/5

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

The description is two sentences plus a list and endpoint, immediately stating the action and scope. No redundant information, well-structured and front-loaded.

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 no output schema, the description includes the return type ('returns the modified object'), the API endpoint, and version. It lacks error handling or prerequisite info but is sufficient for a simple update operation.

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% with each parameter described. The description adds the endpoint and mentions required parameters. However, many parameter descriptions are generic ('JSON request body field') without further explanation. The description does not significantly enhance parameter understanding beyond the 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 the action: 'Updates a line item for a given prime contract.' with a specific verb (updates) and resource (line item), and it distinguishes from other prime contract operations by targeting line items specifically. The title matches the description.

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 says 'Use this to update an existing Prime Contracts' and notes 'only the supplied fields are changed', providing basic context. However, it does not differentiate from sibling tools like 'update_prime_contract_line_item_v1_0' or specify when not to use this tool. No alternatives or exclusions are given.

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