Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Images

list_images
Read-onlyIdempotent

Retrieve a paginated list of images from a Procore project's photo album, with filters for category, dates, location, and more.

Instructions

Return a list of all Images from a Project's Photo Album (Image Category). See Filtering on List Actions for information on using the filtering capabilities provided by this endpoint. Use this to enumerate Photos when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Photos. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Project Management > Photos. Endpoint: GET /rest/v1.0/images

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesQuery string parameter — unique identifier for the project.
image_category_idNoQuery string parameter — optional. ID of the image category to filter the images by.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
filters__daily_log_segment_idNoQuery string parameter — daily Log Segment ID filter
filters__log_dateNoQuery string parameter — date of Photos added to the Daily Log in the format "YYYY-MM-DD", or a range of dates in the format "YYYY-MM-DD...YYYY-MM-DD".
filters__privateNoQuery string parameter — if true, returns only item(s) with a `private` status.
filters__starredNoQuery string parameter — if true, returns only item(s) with a `starred` status.
filters__location_idNoQuery string parameter — location ID. Returns item(s) with the specified Location ID or a range of Location IDs.
filters__include_sublocationsNoQuery string parameter — use together with `filters[location_id]`
filters__trade_idsNoQuery string parameter — array of Trade IDs. Returns item(s) with the specified Trade IDs.
filters__projectionNoQuery string parameter — return items with the specified projection type.
filters__queryNoQuery string parameter — return item(s) containing search query
filters__created_atNoQuery string parameter — return item(s) created within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYYY-MM-...
filters__updated_atNoQuery string parameter — return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYY...
filters__uploader_idNoQuery string parameter — return item(s) uploaded by the specified User IDs
filters__idNoQuery string parameter — return item(s) with the specified IDs.
sortNoQuery string parameter — field to sort by. If the field is passed with a - (EX: -created_at) it is sorted in reverse order
serializer_viewNoQuery string parameter — the data set that should be returned from the serializer. The normal view includes default fields, plus links, comments_count, trades. The android view includes default fields, plus trades, comment...
Behavior4/5

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

The description adds context beyond annotations by mentioning paginated JSON array, pagination metadata, and required parameters, but does not cover aspects like rate limits or response structure in detail.

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 relatively concise and front-loaded with the main purpose, though it includes an API endpoint and link that add length without critical value.

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 high parameter count and complete schema coverage, the description adequately explains pagination, filtering, and required parameters, providing sufficient context for a list tool.

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 description coverage is 100%, so the description adds limited value. It mentions required parameters and pagination controls, but the schema already documents all parameters thoroughly.

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 returns a list of all Images from a Project's Photo Album, specifying the resource, scope, and filtering capabilities. It distinguishes from siblings by focusing on enumeration and pagination.

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 clear guidance on when to use the tool (for paginated overview, finding IDs, filtering) but does not explicitly exclude alternatives or mention when not to use it.

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