Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Prime Contract Line Item

create_prime_contract_line_item_project

Create a line item for a prime contract in Procore to specify costs, quantities, and assign a work breakdown structure code.

Instructions

Creates a line item for a given prime contract. Use this to create a new Prime Contracts in Procore. Creates a new Prime Contracts and returns the created object on success (HTTP 201). Required parameters: company_id, project_id, prime_contract_id, wbs_code_id. Procore API (v2.0): Construction Financials > Prime Contracts. Endpoint: POST /rest/v2.0/companies/{company_id}/projects/{project_id}/prime_contracts/{prime_contract_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.
prime_contract_idYesURL path parameter — unique identifier for the Prime Contract.
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_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 already indicate readOnlyHint=false and destructiveHint=false. The description adds that it returns the created object on HTTP 201, which is expected. No additional behavioral traits (e.g., permissions, duplicate handling) are disclosed, but the endpoint info is useful.

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 includes redundant phrasing ('Creates a new Prime Contracts' repeated) and is somewhat verbose. It contains useful API info but could be more concise and accurate.

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?

Given no output schema, the description adequately mentions the return value and status code. The endpoint path is provided. However, the misleading statement about creating a Prime Contract undermines completeness for a line item tool.

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%, so all parameters are already described. The description only lists required parameters (matching schema), adding no new meaning. Baseline 3 is appropriate.

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

Purpose2/5

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

The description states it creates a line item but then incorrectly claims it creates a new Prime Contracts, causing confusion. The verb 'creates' is clear, but the resource is ambiguous due to the contradiction.

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?

No when-to-use or when-not-to-use guidance is provided. With numerous sibling tools like create_prime_contract_line_item_v1_0, differentiation is absent. The description gives no context for choosing this tool over others.

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