Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Image Category

delete_image_category
DestructiveIdempotent

Permanently delete a photo album (image category) from a specified project. This action cannot be undone.

Instructions

Delete a Photo Album (Image Category) from a specified 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/image_categories/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — iD of the image category
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 convey destructiveHint=true and idempotentHint=true. The description adds that it permanently removes the specified Photos, but this is predictable. Does not disclose additional traits like required permissions or that the action is idempotent (already hinted). Minimal added value 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?

Five sentences with repetition: 'This cannot be undone' appears twice, 'Permanently removes' twice. Front-loaded first sentence is good, but overall could be more concise without sacrificing clarity.

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?

For a simple destructive action, the description is adequate. It mentions the endpoint and API category. However, it lacks details on what exactly is deleted (e.g., all photos in the category) and any prerequisites. No output schema but typical for delete.

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 descriptions for both parameters. The description merely lists required parameters, adding no meaning beyond the schema. Baseline score applies.

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

Purpose4/5

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

Clearly states the tool deletes a photo album/category permanently. Verb and resource are explicit, but the description is slightly repetitive (mentions 'cannot be undone' twice). Distinguishes from sibling delete tools (e.g., delete_image) but does not explicitly differentiate.

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?

Implies use for permanent deletion but provides no guidance on when to use this tool vs alternatives (e.g., delete_image, delete_category). No when-not-to-use or context for selection.

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