Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Punch Item

delete_punch_item
DestructiveIdempotent

Delete a specific Punch Item permanently from a Procore project. This action requires the item ID and project ID and cannot be undone.

Instructions

Delete a specific Punch Item. Use this to permanently delete the specified Punch List records. This cannot be undone. Permanently removes the specified Punch List records. This action cannot be undone. Required parameters: id, project_id. Procore API (v1.1): Project Management > Punch List. Endpoint: DELETE /rest/v1.1/punch_items/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — iD of the Punch Item
project_idYesQuery string parameter — unique identifier for the project.
Behavior3/5

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

Annotations already indicate destructiveHint=true. Description reinforces 'cannot be undone' and 'permanently removes', which adds some value beyond annotations but is not substantial.

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?

Concise with front-loaded action. Minor redundancy ('This cannot be undone' repeated twice) prevents a 5.

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 simple parameters and no output schema, the description adequately covers purpose and consequences. Could mention success status or errors but not critical.

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% with parameter descriptions. Description merely restates required parameters without adding new meaning.

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?

Clearly states 'Delete a specific Punch Item' with verb+resource. Distinguishes from siblings like create, list, update by focusing on 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?

Provides clear context for deletion with warnings about permanence. Does not explicitly mention alternatives or when not to use, but context is sufficient for a simple delete tool.

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