Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Image Category

show_image_category
Read-onlyIdempotent

Get full details of a specific image category (photo album) in a Procore project. Provide the image category ID and project ID to retrieve its complete field set.

Instructions

Return detail information about the specified Photo Album (Image Category). Use this when you already know which image category you want and need its full field set. id must identify an existing parent record — resolve it with the matching list tool first. Returns a single JSON object describing the image category. Read-only — it changes nothing in Procore. 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: GET /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?

Adds valuable context beyond annotations: 'Read-only — it changes nothing in Procore' reinforces readOnlyHint, and it details failure modes (401, 403, 404) and return format (single JSON object). No contradiction with annotations.

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 each sentence earns its place: purpose, usage condition, parameter guidance, behavior, error handling, and endpoint. It is not overly verbose and is effectively front-loaded.

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?

Combined with annotations and schema, the description covers purpose, usage, prerequisites, return type, error semantics, and endpoint. For a simple read-only show tool, this is complete.

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 description coverage is 100%, but the description adds meaning for id by noting it must identify an existing parent record and should be resolved first. This goes beyond the schema's simple parameter definitions.

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 verb 'Return detail information' and the specific resource 'Photo Album (Image Category)'. It distinguishes itself from list tools by noting 'Use this when you already know which image category you want and need its full field set'.

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?

Explicitly says when to use it ('when you already know which image category you want and need its full field set') and instructs to resolve id with the matching list tool first. It does not name the specific list tool (list_image_categories) but clearly implies the prerequisite.

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