Skip to main content
Glama
TylerIlunga

Procore MCP Server

Modify An Existing Markup

modify_an_existing_markup

Update an existing markup on a contract or potential change order with new data. Specify holder type, holder ID, and project ID to modify fields such as name, percentage, or position.

Instructions

Modify an existing Markup with new data for specified holder. This endpoint supports the Contract and Potential Change Order tools. Access requires the user to have admin permissions for the relevant tool. Markups associated with contracts can be updated at any time. Markups on potential change orders can only be updated when the SOV (Schedule of Values) lines are in an editable state. Use this to update an existing Contracts (only the supplied fields are changed). Updates the specified Contracts and returns the modified object on success. Required parameters: project_id, holder_type, holder_id, id. Procore API: Construction Financials > Contracts. Endpoint: PATCH /rest/v1.0/financials/markups/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Contracts resource
project_idYesQuery string parameter — iD of the Markup's Project
holder_typeYesQuery string parameter — type of the Markup's Holder
holder_idYesQuery string parameter — iD of the Markup's Holder
applies_to_allNoJSON request body field — indicates if the markup applies to all change management items within the holder.
compoundNoJSON request body field — details of the compound calculations for the markup.
markup_conditionsNoJSON request body field — conditions that determine how the markup will be applied to change management items within the holder.
markup_setNoJSON request body field — set of the markup. - **Horizontal markup:** Calculates the markup amount on an individual line item. - **Vertical markup:** Calculates the markup amount as a subtotal on all line items on a change ...
nameNoJSON request body field — name of the markup.
percentageNoJSON request body field — percentage value of the markup. The default precision is 50.
positionNoJSON request body field — position of the markup in the markup set of the holder. The default is the next available position, starting at 1.
prime_line_item_idNoJSON request body field — unique identifier for the Prime Contract Line Item associated with the markup. This ensures synchronization between the estimated value (without vertical markup) and the revenue value (with verti...
tax_code_idsNoJSON request body field — list of unique identifiers for tax codes associated with the markup. Applicable only when advanced calculations are enabled.
wbs_code_idNoJSON request body field — iD of the Wbs Code the Markup percentage will be applied to on a project's budget. Default is ID of the `None` Wbs Code.
Behavior3/5

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

Annotations already indicate mutability and non-destructiveness. The description adds that only supplied fields are changed and returns the modified object, but no additional behavioral details beyond annotations.

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 info (API path) and the 'Contracts' error, making it slightly lengthy and less focused. Several sentences could be merged.

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?

Covers permissions, timing, and returns, but lacks details on compound/markup_conditions parameters and does not fully compensate for missing output schema. Minor error 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 description's listing of required parameters adds minimal value. The partial update behavior is implied but not parameter-specific.

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 it modifies an existing markup, distinguishing it from add/remove siblings. However, it mistakenly mentions 'Contracts' instead of 'Markups' in one sentence, slightly reducing clarity.

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 explains when to use the tool (admin permissions required, timing constraints for PCOs) and implies it's for partial updates, but does not explicitly compare to other markup-related siblings.

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