Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Bid Form

delete_bid_form
DestructiveIdempotent

Permanently deletes a specified bid form along with its sections and items from a Procore bid package. This action is irreversible.

Instructions

Delete a single Bid Form and its associated Sections and Items. Use this to permanently delete the specified Bid Management records. This cannot be undone. Permanently removes the specified Bid Management records. This action cannot be undone. Required parameters: project_id, bid_package_id, bid_form_id. Procore API: Preconstruction > Bid Management. Endpoint: DELETE /rest/v1.0/projects/{project_id}/bid_packages/{bid_package_id}/bid_forms/{bid_form_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
bid_package_idYesURL path parameter — unique identifier of the bid package
bid_form_idYesURL path parameter — unique identifier of the bid form
Behavior3/5

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

Annotations already indicate destructive=true and idempotent=true. Description adds the permanence of the action and cascading deletion of associated records, which is useful but not extensive.

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?

Description is concise with several sentences. Front-loaded with key action. Slight repetition of 'permanently delete', but overall efficient.

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?

Given the destructive operation, good annotations, and full schema coverage, the description adequately explains the cascading effect and required IDs. No output schema needed for delete.

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% and each parameter has a clear description. The description merely repeats 'Required parameters' without adding new meaning, so baseline score of 3.

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?

States clearly 'Delete a single Bid Form and its associated Sections and Items', using specific verb and resource. This distinguishes it from sibling tools like 'delete_bid_form_section' or 'delete_bid_form_item'.

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?

Explicitly says to use for permanent deletion and lists required parameters. Does not mention when not to use or provide direct alternatives among siblings, but context is clear.

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