Skip to main content
Glama
TylerIlunga

Procore MCP Server

Deletes A Receipt Line Item.

deletes_a_receipt_line_item
DestructiveIdempotent

Permanently delete a receipt line item after resolving its receipt and line item IDs. Requires an unlocked draft receipt; the action cannot be undone.

Instructions

This endpoint performs a deletion of a Receipt Line Item. The deletion follows these rules: 1. If locked is false: Only then Deletion can be performed as in that case it is a draft Receipt 2. The hard deletion is performed for the specified receipt line. 3. The hard deletion is performed for the connected shipment and shipment lines only if shipment is system generated. 4. The Shipment will be deleted only if there are no shipment lines connected to it. Otherwise only the related shipment line will be deleted. 5. The refdoc_related_id is marked as null in the receipt if the line being deleted is the only line in the receipt. Confirm the target id with the matching show or list tool before calling. company_id and project_id default to the values set by procore_set_config when omitted, and receipt_id, id must identify existing parent records — resolve them with the matching list tool first. Permanently removes the receipt line item. 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: receipt_id, id, company_id, project_id. Procore API (v2.0): Resource Management > Materials Management. Endpoint: DELETE /rest/v2.0/companies/{company_id}/projects/{project_id}/materials_mgmt/receipts/{receipt_id}/line_items/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — receipt line item id
company_idYesURL path parameter — the company identifier
project_idYesURL path parameter — the project identifier
receipt_idYesURL path parameter — unique identifier of the receipt
Behavior5/5

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

Despite annotations already marking this as destructive and idempotent, the description adds extensive behavioral detail: cascade deletion rules for connected shipments, refdoc_related_id nulling, permanence, repeat-call 404, and common error codes. This significantly exceeds what annotations alone convey.

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-structured with numbered deletion rules and clear sections. Some redundancy exists (required parameters list, endpoint URL) but it remains logically organized and front-loaded with the primary action.

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?

The description is thorough for a destructive tool with complex cascading effects, covering preconditions, side effects, error codes, permanence, and id resolution. It loses a point for the minor contradiction about defaulted parameters and for not explicitly stating the success response, though the latter may be unnecessary.

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 baseline is 3. The description adds some resolution guidance (use list tool, confirm target id) but also introduces a confusing statement about company_id/project_id defaulting when omitted, which conflicts with the schema's required flag. This reduces the value of the extra parameter information.

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 this tool deletes a Receipt Line Item, with a specific verb and resource, and includes the exact endpoint. It distinguishes from sibling tools like updates_a_single_receipt_line_item and deletes_a_condition_from_a_receipt_line_item_and_adjusts_line by focusing solely on the line item deletion.

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?

It provides clear usage context: deletion only allowed when locked is false (draft receipt), and instructs the caller to confirm the target id with a show/list tool and resolve parent records. However, it does not explicitly name alternative tools or state when not to use it beyond the locked condition.

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