Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create An Estimate Line Item In The Proposal

create_an_estimate_line_item_in_the_proposal_company

Create a new line item in a Procore proposal to add cost details to a Bid Board project.

Instructions

Create an estimate line item in the proposal. Use this to create a new Bid Board records in Procore. Creates a new Bid Board records and returns the created object on success (HTTP 201). Required parameters: proposal_id, company_id, bid_board_project_id. Procore API (v2.0): Preconstruction > Bid Board. Endpoint: POST /rest/v2.0/companies/{company_id}/estimating/bid_board_projects/{bid_board_project_id}/proposals/{proposal_id}/line_items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
proposal_idYesURL path parameter — unique identifier of the proposal
company_idYesURL path parameter — unique company identifier associated with the Procore User Account.
bid_board_project_idYesURL path parameter — unique BidBoard project identifier
nameNoJSON request body field — display name of the line item.
group_idNoJSON request body field — line item group ID. Omit or leave empty to use the default group.
cost_itemNoJSON request body field — cost item associated with the line item. Provide custom pricing or omit to use a generic cost item based on type. When provided, the entire cost item is replaced (no partial updates).
labor_factorNoJSON request body field — labor difficulty factor applied to the cost item.
tagNoJSON request body field — optional tag for filtering or grouping.
Behavior3/5

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

Annotations already indicate a write operation (readOnlyHint=false). The description adds that it returns the created object on HTTP 201 and provides the endpoint URL. It does not disclose other behaviors like idempotency or side effects, but the annotation coverage is adequate.

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 verbose and repetitive, e.g., 'Use this to create a new Bid Board records' followed by 'Creates a new Bid Board records'. Grammar issues and extraneous API details reduce conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lacks details on response structure, optional parameter usage, and scope (company vs project). It does not explain prerequisites or constraints. The confusing 'Bid Board' term undermines completeness.

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 the description adds no additional meaning beyond listing required parameters. The description does not explain optional parameters or provide examples.

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

Purpose3/5

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

The description states it creates an estimate line item in the proposal, which is clear. However, it conflates 'estimate line item' with 'Bid Board records', causing confusion. It does not differentiate from the sibling tool 'create_an_estimate_line_item_in_the_proposal_project' for company vs project scope.

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?

The description lists required parameters but provides no guidance on when to use this tool versus alternatives like the project variant. No context on prerequisites or scenarios.

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