Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Recycled Incidents

list_recycled_incidents
Read-onlyIdempotent

Retrieve a paginated list of recycled incidents for a project. Filter by ID, date, status, location, and other criteria to find specific deleted incidents.

Instructions

Returns a list of Recycled Incidents for a given 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}/recycle_bin/incidents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
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__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__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__event_dateNoQuery string parameter — returns item(s) with an event date within the specified ISO 8601 datetime range.
filters__location_idNoQuery string parameter — return item(s) with the specified Location IDs.
filters__statusNoQuery string parameter — returns item(s) matching the specified status value.
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.
filters__hazard_idNoQuery string parameter — hazard ID. Returns item(s) with the specified Hazard ID.
filters__time_unknownNoQuery string parameter — if true, returns item(s) where the time of Incident occurrence is unknown.
filters__recordableNoQuery string parameter — return item(s) that are recordable.
filters__queryNoQuery string parameter — return item(s) containing query. Searchable fields include Incident title, Creator, Witness Statement, Incident Action description, Incident Action Type, Contributing Behavior, Contributing Conditi...
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 declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. Description adds pagination details (page, per_page, metadata) and endpoint info, but these are already in schema. No additional behavioral traits 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.

Conciseness5/5

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

Very concise: three sentences covering purpose, usage, pagination, requirements, and API context. Front-loaded with purpose. Every sentence earns its place.

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?

Adequate but assumes domain knowledge of Incident fields. No output schema, so description could detail response structure more. With 16 parameters and no output schema, a bit more completeness would be helpful.

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% with parameter descriptions. The description reiterates page and per_page usage and mentions response metadata, but adds minimal extra meaning beyond the schema.

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?

Clearly states it returns a list of Recycled Incidents for a given project. The verb 'list' and resource 'Recycled Incidents' are specific and distinguish from sibling tools like list_incidents (non-recycled) and list_recycled_actions.

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?

Provides clear usage context: 'enumerate Incidents when you need a paginated overview, to find IDs, or to filter by query parameters.' Implies it is for recycled incidents, but does not explicitly name alternative tools for non-recycled incidents.

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