Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Direct Cost Line Item

update_direct_cost_line_item

Update an existing direct cost line item in a project by modifying fields such as amount, description, or cost code.

Instructions

Update a Direct Cost Line Item. This action does not support concurrent requests. If there is an attempt to update a Direct Cost Line Item that belongs to a Direct Cost which is being updated or deleted by another request, a 409 Conflict error will be returned. Note: A budget line item will automatically be created for Non-budgeted line items for all new projects and for projects enabled with Non-Budgeted line item beta functionality. Use this to update an existing Direct Costs (only the supplied fields are changed). Updates the specified Direct Costs and returns the modified object on success. Required parameters: project_id, direct_cost_id, id. Procore API: Construction Financials > Direct Costs. Endpoint: PATCH /rest/v1.0/projects/{project_id}/direct_costs/{direct_cost_id}/line_items/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
direct_cost_idNoJSON request body field — unique identifier of the direct cost
idYesURL path parameter — direct Cost Line Item ID
amountNoJSON request body field — the amount for this Direct Costs operation
wbs_code_idNoJSON request body field — unique identifier of the wbs code
cost_code_idNoJSON request body field — unique identifier of the cost code
descriptionNoJSON request body field — the description for this Direct Costs operation
extended_typeNoJSON request body field — calculated amount from quantity and unit cost or manually entered amount
quantityNoJSON request body field — quantity of described item
line_item_type_idNoJSON request body field — unique identifier of the line item type
origin_dataNoJSON request body field — the origin data for this Direct Costs operation
origin_idNoJSON request body field — unique identifier of the origin
unit_costNoJSON request body field — unit cost of described item
uomNoJSON request body field — unit of measure of the described item
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?

Annotations indicate readOnlyHint=false and openWorldHint=true. The description adds important behavioral context: no concurrent support, 409 on conflict, and a side effect (budget line item creation). This exceeds what annotations provide. No contradiction with annotations.

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 moderately concise but contains some redundancy (e.g., repeats 'Updates the specified Direct Costs'). It front-loads the purpose but could be trimmed. Includes API endpoint info which may be unnecessary for an agent.

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?

No output schema is provided, but the description mentions 'returns the modified object on success'. It covers concurrency, side effects, and required parameters. However, the inconsistency in required parameters creates confusion. Overall, it is fairly complete for a well-documented schema.

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

Parameters2/5

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

Schema coverage is 100% with parameter descriptions. The description list required parameters inconsistently (schema requires only project_id and id, but description includes direct_cost_id as required). This contradiction reduces reliability. Description does not add meaningful parameter semantics 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 'Update a Direct Cost Line Item.' with a specific verb and resource. It distinguishes from sibling tools like create, delete, list, and sync by stating it updates existing items and only supplied fields change.

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?

Provides explicit guidance on concurrent request handling (409 Conflict), mentions a side effect (budget line item auto-creation for non-budgeted items), and lists required parameters. However, it does not explicitly compare to alternative tools or state when not to use it.

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