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 Procore project. Provide the image category ID and project ID to remove the record irreversibly.

Instructions

Delete a Photo Album (Image Category) from a specified 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 category. 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/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.
Behavior5/5

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

Beyond the annotations (destructiveHint, idempotentHint), the description discloses that deletion is permanent, a repeat call returns 404, and failures return an error payload with specific HTTP statuses. This adds substantial behavioral context.

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 moderately long but every sentence adds value—purpose, preconditions, effects, error behavior, required params, and endpoint reference. It is front-loaded with the core purpose.

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 tool with no output schema, the description covers purpose, safe invocation, permanence, error semantics, required parameters, and API context. It is complete and self-sufficient.

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%, so the baseline is 3. The description adds meaning by specifying that 'id must identify an existing parent record' and must be resolved with a list tool first, which is not in the schema. It also clarifies 'Photo Album' as the resource.

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 the action: 'Delete a Photo Album (Image Category) from a specified Project.' It uses a specific verb and resource, distinguishing it from sibling tools like list_image_categories and create_image_category.

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?

The description provides explicit preconditions: 'Confirm the target id with the matching show or list tool before calling' and 'resolve it with the matching list tool first.' It also explains common failure contexts (401, 403, 404). It does not explicitly state when not to use the tool, but the guidance is otherwise strong.

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