Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Incident Alerts

list_incident_alerts
Read-onlyIdempotent

Retrieve paginated incident alerts from a project. Filter by ID, injury, recipient, severity, or trigger for targeted results.

Instructions

Returns a list of all Incident Alerts associated with a Project. Use this to enumerate Incidents when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Incidents. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Project Management > Incidents. Endpoint: GET /rest/v1.0/projects/{project_id}/incidents/alerts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
incident_idNoQuery string parameter — unique identifier of the incident
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
filters__idNoQuery string parameter — return item(s) with the specified 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__injury_idNoQuery string parameter — return item(s) with the specified Injury IDs.
filters__recipient_idNoQuery string parameter — return item(s) with the specified recipient (User) IDs
filters__severity_level_idNoQuery string parameter — return item(s) with the specified Incident Severity Level IDs
filters__triggered_by_idNoQuery string parameter — return item(s) with the specified triggered by (User) IDs
sortNoQuery string parameter — sort order for results. Prefix with '-' for descending order
Behavior4/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds value by explaining pagination behavior (use page and per_page, response includes pagination metadata) and noting the required parameter project_id. No contradictions.

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 three sentences covering purpose, usage, and pagination details. It also includes Procore API and endpoint info which, while not essential, is not overly verbose. It is well-structured and front-loaded with the key purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description has a notable inconsistency: it first says 'Incident Alerts' but later refers to the result as 'Incidents'. For a tool with 12 parameters and no output schema, it does not summarize the filter options or response structure beyond pagination. This gap reduces completeness.

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 coverage is 100%, so baseline is 3. The description mentions using page and per_page for pagination and states project_id is required, adding a bit of context beyond the schema. However, it does not elaborate on the filter parameters or sort, so value added is modest.

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 list of Incident Alerts associated with a Project, using a specific verb ('Returns a list') and resource ('Incident Alerts'). It distinguishes itself from siblings by mentioning paginated overview and filtering capabilities, which are specific to this tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides use cases like enumerating Incidents, finding IDs, and filtering, but does not explicitly exclude when not to use this tool or mention alternatives like list_incidents or list_incident_alert_recipients. The guidance is present but lacks comparative 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