Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Inspection Item References

list_inspection_item_references
Read-onlyIdempotent

Returns item references for a specific inspection item, enabling discovery of reference details or IDs for use in other Procore API calls. Read-only operation.

Instructions

Returns a collection of Item References for a specified Inspection Item. Use this to discover inspection item references or to look up the id of one before calling a tool that needs it. project_id defaults to the value set by procore_set_config when omitted, and inspection_id must identify an existing parent record — resolve it with the matching list tool first. Returns a JSON array of inspection item references; page and per_page control pagination and the response reports how many pages remain. 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: project_id, inspection_id. Procore API: Project Management > Inspections. Endpoint: GET /rest/v1.0/projects/{project_id}/inspections/{inspection_id}/item_references

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoQuery string parameter — page number for paginated results (default: 1)
sortNoQuery string parameter — sort item(s) by the chosen param; check below for a list of options. The direction of sorting is ascending by default; for descending sort, insert the - symbol before the param.
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
project_idYesURL path parameter — unique identifier for the project.
filters__idNoQuery string parameter — return References with the specified IDs
inspection_idYesURL path parameter — unique identifier for the inspection.
filters__item_idNoQuery string parameter — return Reference(s) with the specified Item IDs
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...
Behavior4/5

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

Beyond annotations (readOnlyHint, destructiveHint), the description adds error payload semantics (401/403/404), pagination behavior ('page and per_page control pagination and the response reports how many pages remain'), and the default project_id from procore_set_config. No contradiction.

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 long but dense; each sentence provides actionable info. It's front-loaded with the main purpose and includes structured error and parameter details. No wasted words.

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?

Despite no output schema, the description explains return format, pagination, error cases, and required parameter dependencies. It also gives the API endpoint and domain area, making it complete for a 9-param list tool.

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 covers all 9 params, but the description adds crucial meaning: project_id defaults to procore_set_config when omitted, and inspection_id must resolve to an existing parent record. These are not in the schema.

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 uses a specific verb 'Returns' and identifies the resource 'Item References for a specified Inspection Item'. It also states the use case of discovering references or looking up IDs before other tools, which distinguishes it from general list tools.

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?

It explicitly says 'Use this to discover inspection item references or to look up the id of one before calling a tool that needs it' and instructs to resolve inspection_id with the matching list tool first. It doesn't name alternative sibling tools but provides clear workflow context.

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