Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update A Line Item Group Of The Proposal

update_a_line_item_group_of_the_proposal_project

Update an existing line item group in a proposal by modifying specified fields such as name, multiplier, notes, or pricing override. Returns the updated object.

Instructions

Update a line item group of the proposal. Use this to update an existing Estimating records (only the supplied fields are changed). Updates the specified Estimating records and returns the modified object on success. Required parameters: proposal_id, line_item_group_id, company_id, project_id. Procore API (v2.0): Preconstruction > Estimating. Endpoint: PATCH /rest/v2.0/companies/{company_id}/projects/{project_id}/estimating/proposals/{proposal_id}/line_item_groups/{line_item_group_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
proposal_idYesURL path parameter — unique identifier of the proposal
line_item_group_idYesURL path parameter — unique identifier of the line item group
company_idYesURL path parameter — unique company identifier associated with the Procore User Account.
project_idYesURL path parameter — unique project identifier
multiplierNoJSON request body field — the multiplier for this Estimating operation
nameNoJSON request body field — the name for this Estimating operation
pricing_overrideNoJSON request body field — the pricing override for this Estimating operation
notesNoJSON request body field — the notes for this Estimating operation
Behavior3/5

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

Annotations provide basic behavioral hints (readOnlyHint false, etc.). The description adds partial update detail and return value, but does not disclose potential side effects despite openWorldHint true.

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 concise with three sentences plus endpoint info. It front-loads the purpose, though the second sentence is slightly redundant.

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 the tool's complexity (8 parameters, no output schema, partial update), the description explains basic behavior but omits return format, nested object details for pricing_override, and side-effects.

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 descriptions already document parameters. The description lists required parameters and endpoint path, adding minimal extra meaning beyond schema.

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

Purpose4/5

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

The description clearly states 'Update a line item group of the proposal' and specifies the verb and resource. However, it does not differentiate from sibling tools like the company version or create/delete tools.

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?

It indicates the tool is for updating existing records and mentions partial update behavior ('only the supplied fields are changed'), but lacks explicit when-to-use vs alternatives or exclusion cases.

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