Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Image

delete_image
DestructiveIdempotent

Permanently remove an image from a Procore project. Specify the image ID and project ID to delete photos. This action cannot be undone.

Instructions

Remove an Image from a Project. Use this to permanently delete the specified Photos. This cannot be undone. Permanently removes the specified Photos. This action cannot be undone. 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
project_idYesQuery string parameter — unique identifier for the project.
permanentNoQuery string parameter — if true, permanently deletes the image.
Behavior3/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds redundancy (repeating 'cannot be undone') and mentions the API endpoint, but does not disclose new behavioral traits beyond annotations.

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

Conciseness3/5

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

The description is repetitive, stating permanent deletion and irreversibility twice. It could be more concise without losing clarity.

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?

No output schema exists, so the description should cover behavior fully. It fails to explain the 'permanent' parameter's role and effect, and repeats content without adding depth.

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. The description only restates required parameters without adding new meaning; the 'permanent' parameter is not mentioned, leaving ambiguity.

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 uses a specific verb 'Remove' and resource 'Image from a Project', and explicitly states permanent deletion. It clearly distinguishes this tool from the many sibling tools.

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

Usage Guidelines3/5

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

The description states when to use (to permanently delete photos) and lists required parameters. It does not provide when-not-to-use or alternative tools for non-permanent deletion.

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