Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Direct Cost Line Item

create_direct_cost_line_item

Add a line item to an existing direct cost in Procore. Automatically creates a budget line item for non-budgeted items.

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. Use this to create a new Direct Costs in Procore. Creates a new Direct Costs and returns the created object on success (HTTP 201). Required parameters: project_id, direct_cost_id. Procore API: Construction Financials > Direct Costs. Endpoint: POST /rest/v1.0/projects/{project_id}/direct_costs/{direct_cost_id}/line_items

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
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 mutation (readOnlyHint false) and non-destructive (destructiveHint false). The description adds behavioral details: concurrent request limitations, 409 error, and automatic budget line item creation for non-budgeted items.

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

Conciseness2/5

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

The description is repetitive (e.g., 'Create a new Direct Cost Line Item' and 'Use this to create a new Direct Costs in Procore'), and includes verbose API reference details that could be condensed.

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?

The description covers concurrency, error scenarios, and auto-creation behavior. However, it lacks output schema or return value details beyond HTTP 201, and omits permission requirements.

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 has 100% coverage so baseline is 3, but the description incorrectly states 'Required parameters: project_id, direct_cost_id'—direct_cost_id is not required in the schema. This misleading statement reduces the score.

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 'Create a new Direct Cost Line Item' using a specific verb and resource. It differentiates from sibling CRUD operations (update, delete, list, sync) by focusing on creation.

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 provides concurrency and error guidance ('does not support concurrent requests', 409 Conflict), but does not explicitly differentiate from sibling 'create_direct_cost_item' or provide when-not-to-use advice.

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