Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Injuries

list_injuries
Read-onlyIdempotent

Retrieve a paginated list of injuries for a given Procore project. Filter by incident, body part, affliction type, and more to find specific incidents.

Instructions

Returns a list of Injuries for a given project. NOTE: The afflictions and affected_body_part keys are deprecated. Please disregard and use the affected_body_parts and affliction_type keys as documented below. 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/injuries

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
incident_idNoQuery string parameter — incident ID. When provided, the list will be scoped to only the Injuries for a given 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__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__affected_company_idNoQuery string parameter — array of Company IDs. Returns item(s) with the specified affected Company IDs.
filters__affected_party_idNoQuery string parameter — array of Affected Party IDs. Returns item(s) with the specified Affected Party IDs.
filters__affected_person_idNoQuery string parameter — array of Person IDs. Returns item(s) with the specified affected Person IDs.
filters__harm_source_idNoQuery string parameter — array of Harm Source IDs. Returns item(s) with the specified Harm Source IDs.
filters__work_activity_idNoQuery string parameter — array of Work Activity IDs. Returns item(s) with the specified Work Activity IDs.
filters__managed_equipment_idNoQuery string parameter — return item(s) with the specified Managed Equipment ID.
filters__recordableNoQuery string parameter — return item(s) that are recordable.
filters__affected_body_partNoQuery string parameter — return item(s) with any of the specified Affected Body Parts.
filters__affliction_type_idNoQuery string parameter — return item(s) with the specified Affliction Type IDs
filters__body_part_idNoQuery string parameter — return item(s) with the specified Body Part IDs
filters__filing_typeNoQuery string parameter — return item(s) with the specified filing types. The `recordable` filing_type filter value is deprecated.
filters__queryNoQuery string parameter — return item(s) containing query
sortNoQuery string parameter — sort order for results. Prefix with '-' for descending order
Behavior3/5

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

Annotations already indicate readOnly, destructive=false, idempotent=true. Description adds value by noting deprecated keys in the response and basic pagination behavior. However, it does not describe response structure or potential rate limits, and the mention of 'Incidents' creates some confusion. Overall, it adds moderate context beyond 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?

Description is reasonably concise, front-loads the core purpose, and includes only essential additional details (deprecation notes, pagination, endpoint). It could be slightly more concise by avoiding repetition of 'Incidents', but overall well-structured.

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

Completeness3/5

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

No output schema exists, so description should cover return format. It mentions 'paginated JSON array of Incidents' and 'pagination metadata', but does not describe fields of an injury object. For a complex tool with many filters and no output schema, this is adequate but not thorough.

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 baseline is 3. Description only adds generic comments about pagination ('Use page and per_page to control pagination') and notes required parameters, which are already in schema. No deeper semantic explanation of parameters is provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it returns a list of Injuries for a project, with specific verb 'returns a list'. However, it confusingly mentions 'Incidents' in two places, which could mislead an agent into thinking it lists incidents rather than injuries. This minor inconsistency slightly reduces clarity.

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?

Description provides usage context: 'Use this to enumerate Incidents when you need a paginated overview, to find IDs, or to filter by query parameters.' It also notes required parameters. But it does not specify when NOT to use this tool or mention alternatives among the many sibling list tools, leaving the agent without exclusion guidance.

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