Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Grouped Recycled Checklists (Inspections)

list_grouped_recycled_checklists_inspections
Read-onlyIdempotent

Retrieve paginated, grouped recycled inspections in a Procore project. Filter by date, type, inspector, template, location, and more to locate IDs or get an overview.

Instructions

Lists Recycled Checklist (Inspections) in a specified Project grouped by a specified attribute. By default the Checklists are grouped by template. See Filtering on List Actions for information on using the filtering capabilities provided by this endpoint. Use this to enumerate Inspections when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Inspections. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Project Management > Inspections. Endpoint: GET /rest/v1.0/projects/{project_id}/recycle_bin/checklist/lists/grouped_index

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__inspection_dateNoQuery string parameter — return item(s) with inspection date within the specified ISO 8601 date range.
filters__inspection_type_idNoQuery string parameter — array of Inspection Type IDs. Return item(s) associated with the specified Inspection Type IDs.
filters__inspector_idNoQuery string parameter — array of User IDs. Return item(s) where the specified User IDs are inspectors.
filters__list_template_idNoQuery string parameter — array of Checklist Template IDs. Return item(s) associated with the specified Checklist Template IDs.
filters__location_idNoQuery string parameter — location ID. Returns item(s) with the specified Location ID or a range of Location IDs.
filters__managed_equipment_idNoQuery string parameter — return item(s) with the specified Managed Equipment ID.
filters__point_of_contact_idNoQuery string parameter — array of User IDs. Return item(s) where the specified User IDs are the point of contact.
filters__spec_section_idNoQuery string parameter — array of Specification Section IDs. Return item(s) associated to the specified Specification Section IDs.
filters__responsible_contractor_idNoQuery string parameter — array of Vendor IDs. Return item(s) where the specified Vendor IDs are the responsible contractor.
filters__closed_by_idNoQuery string parameter — array of User IDs. Return item(s) closed by the specified User ID.
filters__created_by_idNoQuery string parameter — return item(s) created by the specified User IDs
filters__statusNoQuery string parameter — return item(s) with the specified statuses
filters__trade_idNoQuery string parameter — filter results by trade id
filters__queryNoQuery string parameter — return item(s) containing search query
filters__due_atNoQuery string parameter — return item(s) due within the specified date range.
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__closed_atNoQuery string parameter — returns item(s) closed within the specified ISO 8601 datetime range.
sortNoQuery string parameter — sort order for results. Prefix with '-' for descending order
group_byNoQuery string parameter — the group by for this Inspections operation
Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. The description adds operational details: pagination metadata, grouping capability, and a link to filtering documentation. It does not contradict annotations. It effectively supplements the structured data.

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 efficient: two sentences plus a link. It front-loads the main purpose and key parameters (project_id, page, per_page). The link to filtering documentation is useful but may distract. Still, it earns its place without being verbose.

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

Completeness4/5

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

Given the high parameter count (24) and no output schema, the description provides a solid overview: resource type, grouping, pagination, filtering, and required parameter. It does not explain the concept of 'recycled', but that is clear from the tool name and title. It is sufficiently complete for an agent.

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 parameters are well-documented there. The description adds minimal extra meaning: default grouping by template and a reference to filtering docs. This is helpful but does not significantly elevate understanding beyond the schema. Baseline 3 is appropriate.

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 lists recycled checklist inspections grouped by a specified attribute, with pagination and filtering. It specifies the resource (recycled inspections), the action (list), and the grouping. However, it could better distinguish from the non-recycled sibling (list_grouped_checklists_inspections) by explicitly noting that this returns soft-deleted items.

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 context: enumerating inspections for paginated overview, ID finding, or filtering. It does not mention when NOT to use it or alternatives like the non-recycled version. It lacks explicit exclusion guidance, which is needed given the sibling.

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