Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Recycled Injuries

list_recycled_injuries
Read-onlyIdempotent

Retrieve paginated recycled injuries for a project or incident. Filter by date, company, body part, and more to locate specific records.

Instructions

Returns a list of Recycled Injuries for a given project (or Incident, if incident_id is present). 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}/recycle_bin/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 Recycled Injuries for a given Incident. NOTE: The afflictions and affected_body_part keys are deprecated. Please disregard and use t...
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__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
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
Behavior3/5

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

The description adds context beyond annotations: it mentions pagination, required parameters, and deprecation of keys. However, it confusingly refers to 'Incidents' in the output description while the tool is named for injuries, which may mislead an agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is overly verbose, including unnecessary endpoint path and API source. The note about deprecated keys is important but could be placed more concisely. The core purpose is front-loaded but overall structure is inefficient.

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?

Given the complexity (17 parameters, no output schema), the description lacks essential context: it does not explain what 'Recycled' means (e.g., deleted items), describe the output structure beyond 'JSON array', or detail pagination metadata. The mention of 'Incidents' instead of 'Injuries' adds confusion.

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 the schema already documents all parameters. The description reiterates that project_id is required and that page/per_page control pagination, but adds no new meaning beyond what the schema provides.

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?

The description clearly states it returns a list of Recycled Injuries for a given project or incident. It specifies the resource and scope, but does not explicitly differentiate from sibling tools like list_injuries, relying on the name to imply recycled status.

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 usage guidance: 'Use this to enumerate Incidents when you need a paginated overview, to find IDs, or to filter by query parameters.' However, it does not mention when not to use it or suggest alternatives for active injuries.

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