Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete An Inspection Item Attachment

delete_an_inspection_item_attachment
DestructiveIdempotent

Permanently remove an attachment from a specific inspection item using project, inspection, and attachment IDs. This action cannot be undone.

Instructions

Removes the Attachment for a specified Inspection Item on a given Project. Use this to permanently delete the specified Inspections. This cannot be undone. Permanently removes the specified Inspections. This action cannot be undone. Required parameters: project_id, inspection_id, id. Procore API: Project Management > Inspections. Endpoint: DELETE /rest/v1.0/projects/{project_id}/inspections/{inspection_id}/item_attachments/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
inspection_idYesURL path parameter — unique identifier for the inspection.
idYesURL path parameter — unique identifier of the Inspections resource
Behavior1/5

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

The description misstates the action as deleting inspections rather than an attachment, which is a major behavioral contradiction. Annotations already provide destructiveHint=true and idempotentHint=true, and the description adds little beyond 'cannot be undone', but the error undermines transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description repeats 'This cannot be undone' and 'Permanently removes the specified Inspections' twice each. The repetition is unnecessary and the incorrect statement makes it less reliable. The structure is front-loaded correctly, but the redundancy and error reduce conciseness.

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

Completeness2/5

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

The description fails to accurately state that the tool deletes an attachment, not inspections. It also does not mention response behavior or other contextual details. Given the simple operation and existing annotations, this is a fundamental completeness failure.

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 the description merely lists required parameters without adding meaning beyond what the schema already provides. No additional information about formats, defaults, or relationships.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence correctly states 'Removes the Attachment', but the description then incorrectly says 'permanently delete the specified Inspections' twice, creating confusion about the tool's actual purpose. The name and title are clear, but the description undermines that clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, such as other delete attachment tools. It only states required parameters and that the action is irreversible, but provides no comparative context.

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