Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Attachment

delete_attachment_project
DestructiveIdempotent

Permanently delete an attachment from a Procore inspection checklist. Specify project, list, and attachment IDs to remove the file from the system.

Instructions

Deletes the specified Attachment. Confirm the target id with the matching show or list tool before calling. project_id defaults to the value set by procore_set_config when omitted, and list_id, id must identify existing parent records — resolve them with the matching list tool first. Permanently removes the attachment. 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: project_id, list_id, id. Procore API: Project Management > Inspections. Endpoint: DELETE /rest/v1.0/projects/{project_id}/checklist/lists/{list_id}/attachments/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Inspections resource
list_idYesURL path parameter — checklist (Inspection) ID
project_idYesURL path parameter — unique identifier for the project.
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds important context: permanent deletion, non-reversibility, 404 on repeat calls, and error payload details. This goes beyond the structured annotations.

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

Conciseness5/5

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

The description is dense but every sentence adds necessary information: prerequisites, permanence, error handling, required parameters, and endpoint. It is well-structured with no redundant wording.

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

Completeness5/5

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

For a destructive delete tool, it covers confirmation steps, idempotency behavior, failure modes, and parameter requirements. The absence of an output schema is compensated by explicit error semantics. The description is fully sufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for each parameter. The description adds practical semantics: project_id defaults to config value when omitted, and list_id/id must identify existing parent records. This is valuable beyond the schema.

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 opens with 'Deletes the specified Attachment', a clear verb and resource. It further specifies the exact API endpoint and resource path, distinguishing it from other delete tools. The scope is unambiguous.

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 explicitly instructs to 'Confirm the target id with the matching show or list tool before calling' and to resolve parent records first, providing clear prerequisite context. It does not name alternative tools, but the guidance is specific and actionable.

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