Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Image Category

update_image_category

Update an existing photo album's name, privacy, or cover image in a Procore project by providing the album and project IDs.

Instructions

Update a Photo Album (Image Category) in a specified Project. Use this to update an existing Photos (only the supplied fields are changed). Updates the specified Photos and returns the modified object on success. Required parameters: id, project_id, name. Procore API: Project Management > Photos. Endpoint: PATCH /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.
nameYesJSON request body field — the Name of the Image Category
privateNoJSON request body field — the Private status of the Image Category
album_cover_idNoJSON request body field — iD of an Image that is the cover Image of the Image Category.
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds that it performs a partial update (PATCH), returns the modified object, and requires specific parameters. This provides modest 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.

Conciseness5/5

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

The description is concise (three sentences) and front-loaded with the main purpose. Every sentence contributes meaningful information: purpose, partial update behavior, return value, required parameters, and API reference.

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

Completeness4/5

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

Given the tool's simplicity (5 params, 100% schema coverage, annotations present), the description adequately covers the update operation. It misses potential details like error handling or permission requirements, but for an update with non-destructive annotations, it is sufficiently complete.

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?

The input schema has 100% parameter description coverage, so the baseline is 3. The description does not add new semantics beyond listing required parameters; it does not explain the meaning of 'private' or 'album_cover_id' beyond what the schema provides.

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 tool's purpose: 'Update a Photo Album (Image Category) in a specified Project.' It specifies partial update behavior ('only the supplied fields are changed') and distinguishes from sibling tools like create_image_category or delete_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 indicates usage by stating 'Use this to update an existing Photos' and lists required parameters. However, it does not explicitly exclude scenarios or compare with alternative tools like batch updates or creating new categories.

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