Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Bid Form Item

delete_bid_form_item
DestructiveIdempotent

Permanently remove a single bid form item from a Procore bid package. Irreversible action requiring project, bid package, and item IDs.

Instructions

Delete single Bid Form Item. 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_item_id. Procore API: Preconstruction > Bid Management. Endpoint: DELETE /rest/v1.0/projects/{project_id}/bid_packages/{bid_package_id}/bid_form_items/{bid_form_item_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_item_idYesURL path parameter — unique identifier of the bid form item
Behavior4/5

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

The description reinforces the destructiveHint annotation by stating 'This cannot be undone' and 'Permanently removes', and adds context about required parameters and the API endpoint. No contradictions with 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 somewhat repetitive, stating the irreversible nature twice and including redundant phrases. While front-loaded with the main purpose, it could be more concise.

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 tool is a delete operation with full schema coverage and appropriate annotations, the description provides sufficient context: the resource, required parameters, and irreversibility. No output schema needed.

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?

All three parameters are fully documented in the schema (100% coverage). The description lists them but adds no additional meaning beyond what the schema already provides, so baseline score applies.

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 'Delete single Bid Form Item' and specifies the resource as 'Bid Management records'. It uses a specific verb and resource, distinguishing it from sibling delete tools for bid forms or sections.

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 explicitly says 'Use this to permanently delete' and notes the action is irreversible, providing clear context for when to use. However, it does not mention when not to use or list alternatives.

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