Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Budget Modification (Deprecated)

update_budget_modification
Idempotent

Update a budget modification in Procore when Budget Changes are disabled, setting transfer amount and target line item.

Instructions

Update a Budget Modification only if Budget Changes are not enabled. This endpoint will be deprecated at October 16th of 2023. For more information on the Budget Changes API, see our documentation on upgrading from the Budget Modifications API to the Budget Changes API. DEPRECATED: Procore has deprecated this endpoint (as of 2022-11-17). It may be removed without further notice; prefer a newer version of this resource where one exists, and use procore_search_endpoints to find it. Send only the fields you intend to change; omitted fields keep their current values. Pass the record's fields as top-level arguments — they are nested under "budget_modification" in the request payload for you. project_id defaults to the value set by procore_set_config when omitted, and id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified budget modification on success. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: project_id, id, to_budget_line_item_id, transfer_amount. Procore API: Construction Financials > Budget. Endpoint: PATCH /rest/v1.0/projects/{project_id}/budget_modifications/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Budget resource
notesNoJSON request body field — notes on the purpose of the transfer
origin_idNoJSON request body field — the Origin ID to associate with this Budget Modification (must be unique within a company)
project_idYesURL path parameter — unique identifier for the project.
origin_dataNoJSON request body field — the Origin Data to associate with this Budget Modification
transfer_amountYesJSON request body field — the transfer amount for this Budget operation
to_budget_line_item_idYesJSON request body field — iD of the Budget Line Item to transfer to. NOTE: You may not pass the same to_budget_line_item_id as from_budget_line_item_id.
from_budget_line_item_idNoJSON request body field — iD of the Budget Line Item to transfer from. NOTE 1: required if 'Allow Budget Modifications Which Modify Grand Total' is not checked. NOTE 2: When updating if you want to remove the from_budget_li...
Behavior5/5

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

Annotations declare readOnly=false, idempotent=true, and destructive=false, but the description adds substantial behavioral context not captured there: partial-update semantics ('omitted fields keep their current values'), payload nesting behavior, project_id default from procore_set_config, the return value, and common HTTP error codes (401, 403, 404). There is no contradiction with the annotations.

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 long but well-organized, covering purpose, deprecation, usage, update semantics, defaults, and errors. However, deprecation is mentioned twice ('will be deprecated at October 16th of 2023' and 'DEPRECATED: Procore has deprecated this endpoint as of 2022-11-17'), causing minor redundancy and slight timing inconsistency, which could be streamlined.

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

Completeness4/5

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

With no output schema, the description correctly specifies the return value and failure modes. It covers prerequisites, deprecation, migration path, partial update behavior, and default handling. It lacks details on what 'Budget Changes are not enabled' means operationally, but links to docs, making it adequate for tool selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already documents all 8 parameters (100% coverage), so the description need not repeat basic meaning. It adds operational nuance: partial updates, project_id defaulting to config, fields being top-level arguments despite nested payload, and the requirement to resolve id beforehand. This value goes beyond the schema, though it doesn't enrich each parameter individually.

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 opens with 'Update a Budget Modification,' naming the specific verb and resource. It further clarifies the tool's distinct scope by noting the condition 'only if Budget Changes are not enabled' and states the return value ('Returns the modified budget modification'), clearly separating it from create/show/delete/list siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage conditions: 'only if Budget Changes are not enabled' and directs users away in favor of the newer Budget Changes API ('prefer a newer version... use procore_search_endpoints to find it'). It also instructs to resolve the id with 'the matching list tool first,' giving clear when/how-to-use guidance.

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