Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Direct Cost Line Item

create_direct_cost_line_item

Create a new direct cost line item in Procore by supplying project and direct cost IDs, with optional fields like amount, quantity, unit cost, tax code, and description.

Instructions

Create a new Direct Cost Line Item. This action does not support concurrent requests. If there is an attempt to create 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. Pass the record's fields as top-level arguments — they are nested under "line_item" in the request payload for you. project_id defaults to the value set by procore_set_config when omitted, and direct_cost_id must identify an existing parent record — resolve it with the matching list tool first. Acts on the direct cost line item and returns Procore's response for the operation. 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: project_id, direct_cost_id. Procore API: Construction Financials > Project Level Direct Costs. Endpoint: POST /rest/v1.0/projects/{project_id}/direct_costs/{direct_cost_id}/line_items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uomNoJSON request body field — unit of measure of the described item
amountNoJSON request body field — the amount for this Project Level Direct Costs operation
quantityNoJSON request body field — quantity of described item
origin_idNoJSON request body field — unique identifier of the origin
unit_costNoJSON request body field — unit cost of described item
project_idYesURL path parameter — unique identifier for the project.
descriptionNoJSON request body field — the description for this Project Level Direct Costs operation
origin_dataNoJSON request body field — the origin data for this Project Level Direct Costs operation
tax_code_idNoJSON request body field — unique identifier of the tax code
wbs_code_idNoJSON request body field — unique identifier of the wbs code
cost_code_idNoJSON request body field — unique identifier of the cost code
extended_typeNoJSON request body field — calculated amount from quantity and unit cost or manually entered amount
direct_cost_idYesURL path parameter — unique identifier of the direct cost
line_item_type_idNoJSON request body field — unique identifier of the line item type
Behavior5/5

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

Beyond annotations (readOnlyHint false, idempotentHint false), the description adds substantial behavioral context: no concurrent request support, 409 conflict when parent is being updated/deleted, automatic budget line item creation for non-budgeted items, project_id defaulting from procore_set_config, and error payload details (401/403/404). No contradiction with annotations exists.

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 but every sentence carries essential information for a complex mutation tool. It front-loads the action and then covers concurrency, side effects, parameter handling, errors, and API reference. While it could be restructured with clearer separations, the density is justified by the complexity of the operation.

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?

Given the tool's complexity (14 parameters, write operation, side effects, error conditions), the description is remarkably complete. It covers prerequisites, concurrency, automatic budget line item side effects, default behavior, error payloads, required parameters, and the exact API endpoint. This is sufficient for an agent to select and invoke the tool correctly without needing an output schema.

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% with descriptions for all 14 parameters, giving a baseline of 3. The description adds value by explaining that record fields are passed as top-level arguments (though nested under 'line_item' in the payload), that project_id defaults to procore_set_config, and that direct_cost_id must reference an existing parent record. This contextualizes the parameters beyond the schema's field explanations.

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 opens with 'Create a new Direct Cost Line Item,' which is a specific verb+resource statement. It distinguishes the tool from siblings like list_direct_cost_line_items and update_direct_cost_line_item, and clarifies the operation targets line items under a direct cost. The endpoint URL further disambiguates the exact resource path.

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?

The description provides clear usage context: it states the prerequisite that direct_cost_id must identify an existing parent record and advises resolving it with 'the matching list tool first.' It also warns about concurrent request limitations and 409 errors. However, it does not explicitly mention when not to use this tool or name alternative create tools, though siblings like create_direct_cost_item exist.

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