Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Image

delete_image
DestructiveIdempotent

Delete an image from a Procore project permanently. Confirm the image id with the list tool first, then supply the id and project_id to remove it.

Instructions

Remove an Image from a Project. Confirm the target id with the matching show or list tool before calling. id must identify an existing parent record — resolve it with the matching list tool first. Permanently removes the image. 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: id, project_id. Procore API: Project Management > Photos. Endpoint: DELETE /rest/v1.0/images/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Photos resource
permanentNoQuery string parameter — if true, permanently deletes the image.
project_idYesQuery string parameter — unique identifier for the project.
Behavior5/5

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

Adds critical behavioral details beyond annotations: 'Permanently removes the image. This cannot be undone, and a repeat call returns 404.' It also discloses common HTTP error statuses, enhancing failure-mode understanding.

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 dense and well-organized, but contains redundancy between 'Confirm the target id' and 'resolve it with the matching list tool first,' which could be tightened.

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

Completeness3/5

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

It covers deletion semantics, error handling, and required parameters, but omits any mention of the 'permanent' boolean parameter, which is a key part of the tool's behavior. Success response format is also unaddressed, though no output schema exists.

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

Parameters2/5

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

Schema coverage is 100%, but the description adds misleading semantics by calling id an 'existing parent record,' which contradicts the schema's definition as the image identifier. It provides no additional value for the permanent flag or project_id 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 clearly states 'Remove an Image from a Project,' specifying the verb and resource, and distinguishes it from sibling tools like delete_image_category. It also includes the endpoint and API context.

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 the agent to resolve the id with a show/list tool before calling, which is a concrete prerequisite. However, it doesn't contrast with alternatives (e.g., soft-delete) or state when not to use it.

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