Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Incidents

list_incidents
Read-onlyIdempotent

List incidents for a project with filters for date, location, status, and full-text search to locate specific incidents or obtain their IDs.

Instructions

Returns a paginated list of incidents for the specified project, ordered by descending number by default. Each incident includes summary information, associated records count, and linked resources (location, contributing factors, assignees). Supports filtering by date, location, status, root cause fields, recordable flag, and full-text search across title, creator, witness statements, actions, and related fields. Use filters[query] for keyword search. Use this to discover incidents 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. Returns a JSON array of incidents; 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. Procore API: Project Management > Incidents. Endpoint: GET /rest/v1.0/projects/{project_id}/incidents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoQuery string parameter — page number for paginated results (default: 1)
sortNoQuery string parameter — sort order for results. Prefix with '-' for descending order
per_pageNoQuery string parameter — number of items returned per page (Min: 1, Max: 1000). Defaults to 1000 when parameter is not provided.
project_idYesURL path parameter — unique identifier for the project.
filters__idNoQuery string parameter — return item(s) with the specified IDs.
filters__queryNoQuery string parameter — full-text search across incident title, creator name, witness statements, action descriptions, action types, contributing behaviors, contributing conditions, hazards, and location names. Returns in...
filters__statusNoQuery string parameter — returns item(s) matching the specified status value.
filters__type_idNoQuery string parameter — return item(s) with a specific Type ID or a range of Type IDs.
filters__hazard_idNoQuery string parameter — hazard ID. Returns item(s) with the specified Hazard ID.
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__event_dateNoQuery string parameter — returns item(s) with an event date within the specified ISO 8601 datetime range.
filters__recordableNoQuery string parameter — return item(s) that are recordable.
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__assignee_idNoQuery string parameter — return item(s) with a specific Assignee ID or a range of Assignee IDs.
filters__location_idNoQuery string parameter — return item(s) with the specified Location IDs.
filters__time_unknownNoQuery string parameter — if true, returns item(s) where the time of Incident occurrence is unknown.
filters__custom_status_idNoQuery string parameter — return item(s) with the specified Custom Status IDs
filters__contributing_behavior_idNoQuery string parameter — contributing Behavior ID. Returns item(s) with the specified Contributing Behavior ID.
filters__contributing_condition_idNoQuery string parameter — contributing Condition ID. Returns item(s) with the specified Contributing Condition ID.
Behavior4/5

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

Beyond the readOnlyHint annotation, the description adds valuable behavioral context: pagination semantics (page/per_page, pages remaining), project_id defaulting from procore_set_config, and failure modes with HTTP status codes (401, 403, 404). It also explicitly states the tool is read-only, reinforcing the annotation. No contradictions 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 a single dense paragraph but well-structured, front-loading the core function and then covering filters, usage, default behavior, return shape, safety, and errors. Every sentence adds value; no fluff or redundancy, though it could potentially be broken into bullets for easier scanning.

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 tool with 19 parameters and no output schema, the description covers return type (JSON array), pagination behavior, default project_id, filtering capabilities, error payloads, and the broader use case. It is comprehensive enough for an agent to invoke correctly without additional documentation.

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 baseline is 3. The description adds extra meaning by explaining the default sort order, how to use filters[query] for full-text search, project_id defaulting, and pagination controls, which go beyond the raw schema descriptions.

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 paginated list of incidents for the specified project, including specific contents (summary information, records count, linked resources). It distinguishes itself by framing its use as a discovery/id-lookup step before calling a tool that needs an incident id, which differentiates it from 'show_incident' siblings.

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 provides explicit context for when to use the tool ('Use this to discover incidents or to look up the id of one before calling a tool that needs it') and mentions the project_id default behavior. It does not explicitly name alternatives like show_incident, but the guidance is clear and sufficient for an agent to make a selection.

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