Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Budget Modification (Deprecated)

delete_budget_modification
DestructiveIdempotent

Delete a budget modification permanently from a Procore project when Budget Changes are not enabled. Deprecated; prefer the Budget Changes API.

Instructions

Delete 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. Confirm the target id with the matching show or list tool before calling. 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. Permanently removes the budget modification. This cannot be undone, and a repeat call returns 404. 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. Procore API: Construction Financials > Budget. Endpoint: DELETE /rest/v1.0/projects/{project_id}/budget_modifications/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Budget resource
project_idYesURL path parameter — unique identifier for the project.
Behavior5/5

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

The description discloses permanent, irreversible deletion, notes that a repeat call returns 404, and lists common failure statuses (401, 403, 404). This adds meaningful behavioral context beyond the destructiveHint and idempotentHint 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 is verbose and contains redundant deprecation statements ("will be deprecated at October 16th of 2023" and "DEPRECATED: ... as of 2022-11-17"). It is front-loaded with the core action but could be more concise.

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

Completeness5/5

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

It covers the usage condition, deprecation and migration path, prerequisites, destructive behavior, error handling, parameter defaults, and the API endpoint. This is comprehensive for a delete operation with no output schema.

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?

While the schema already covers both parameters, the description adds valuable semantics: project_id defaults to the procore_set_config value, and id must identify an existing parent record. This helps the agent correctly resolve parameters.

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 clearly states the action and resource: "Delete a Budget Modification" and "Permanently removes the budget modification." It distinguishes from sibling tools like show/update_budget_modification by the delete verb and the condition about Budget Changes.

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?

It explicitly says "only if Budget Changes are not enabled," and directs users to the Budget Changes API and procore_search_endpoints for alternatives. It also instructs to confirm the target id with a show or list tool before calling.

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