Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Incident Alerts

list_incident_alerts
Read-onlyIdempotent

Retrieve a paginated list of incident alerts for a Procore project. Filter by incident ID to find specific alerts or obtain an ID for subsequent operations.

Instructions

Returns a paginated list of all incident alerts for the specified project. Optionally scope to a single incident by providing incident_id. Use this to discover incident alerts 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 incident alerts; 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/alerts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoQuery string parameter — page number for paginated results (default: 1)
sortNoQuery string parameter — sort results by the specified field.
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 item(s) with the specified IDs.
incident_idNoQuery string parameter — unique identifier of the incident
filters__injury_idNoQuery string parameter — return item(s) with the specified Injury IDs.
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__incident_idNoQuery string parameter — return item(s) with the specified Incident IDs.
filters__recipient_idNoQuery string parameter — return item(s) with the specified recipient (User) IDs
filters__filing_type_idNoQuery string parameter — return item(s) with the specified Incident Filing Type IDs.
filters__triggered_by_idNoQuery string parameter — return item(s) with the specified triggered by (User) IDs
filters__severity_level_idNoQuery string parameter — return item(s) with the specified Incident Severity Level IDs
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint, but the description adds concrete behavioral details: pagination behavior (page/per_page and remaining pages), error payload handling (401/403/404), and the project_id default behavior. No contradiction with annotations; the 'Read-only' statement reinforces annotations rather than adding new information.

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 dense but well-structured: what it does, when to use, defaults, return format, safety, error cases, and API endpoint. Every sentence adds value with no fluff, and key information is 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?

Given 13 parameters and no output schema, the description effectively covers the essential invocation context: purpose, usage, pagination, error responses, read-only nature, required parameters, and API reference. The schema covers the remaining parameter details, leaving no significant gaps for an agent.

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 meaning beyond the schema by explaining project_id's default from procore_set_config (though schema marks it required, creating a minor inconsistency), incident_id's role in scoping, and pagination semantics. It does not discuss all filters, but the schema provides those details.

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 it 'Returns a paginated list of all incident alerts for the specified project' with explicit scope (project_id, optional incident_id). It distinguishes itself from sibling tools by noting optional scoping to a single incident and its role in 'discover[ing] incident alerts or look[ing] up the id of one before calling a tool that needs it.'

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 incident alerts or to look up the id of one before calling a tool that needs it,' and explains when to scope by incident_id. It also notes the project_id default from procore_set_config, but does not explicitly name alternative tools or provide 'when not to use' exclusions.

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