Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Checklists (Deprecated)

list_checklists
Read-onlyIdempotent

Retrieve checklists (inspections) for a Procore project, with filters for status, due date, location, and template. Discover checklist IDs before using other Procore tools.

Instructions

Lists 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. DEPRECATED: Procore has deprecated this endpoint (as of 2022-01-24). It may be removed without further notice; prefer a newer version of this resource where one exists, and use procore_search_endpoints to find it. Use this to discover checklists or to look up the id of one before calling a tool that needs it. Returns a JSON array of checklists; page and per_page control pagination and the response reports how many pages remain. Read-only — it changes nothing in Procore. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: project_id. Procore API: Project Management > Inspections. Endpoint: GET /rest/v1.0/checklist/lists

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for paginated results (default: 1, 1-indexed)
per_pageNoNumber of items per page (default: 100, max: 100)
project_idYesQuery string parameter — unique identifier for the project.
filters__viewNoQuery string parameter — if 'recycle', return deleted Checklists.
filters__due_atNoQuery string parameter — return item(s) due within the specified date range.
filters__searchNoQuery string parameter — returns item(s) matching the specified search query string.
filters__statusNoQuery string parameter — returns item(s) matching the specified status value.
filters__trade_idNoQuery string parameter — filter results by trade id
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__location_idNoQuery string parameter — filters by specific location (Note: Use *either* this or location_id_with_sublocations, but not both)
filters__inspector_idNoQuery string parameter — array of User IDs. Return item(s) where the specified User IDs are inspectors.
filters__spec_section_idNoQuery string parameter — array of Specification Section IDs. Return item(s) associated to the specified Specification Section IDs.
filters__list_template_idNoQuery string parameter — array of Checklist Template IDs. Return item(s) associated with the specified Checklist Template IDs.
filters__inspection_type_idNoQuery string parameter — array of Inspection Type IDs. Return item(s) associated with the specified Inspection Type IDs.
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__responsible_contractor_idNoQuery string parameter — array of Vendor IDs. Return item(s) where the specified Vendor IDs are the responsible contractor.
Behavior4/5

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

Adds meaningful behavioral context beyond annotations: pagination behavior ('page and per_page control pagination and the response reports how many pages remain'), error payload details ('common 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve'), and default grouping ('grouped by template'). The read-only statement aligns with annotations, with no contradiction.

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 somewhat long but well-structured, with purpose front-loaded and each sentence earning its place (purpose, link, deprecation, use case, return, errors, endpoint). It remains readable without excessive redundancy.

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?

Covers essential operational context: return format (JSON array), pagination, error handling, deprecation, and usage guidance. No output schema exists, so the description's mention of return type is helpful. Could be slightly more explicit about how the grouping attribute is configured, but overall it is complete for a list action.

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. The description adds little parameter-specific value beyond restating the required project_id; it mentions grouping by 'a specified attribute' but does not identify which parameter controls this, leaving a small gap.

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 'Lists Checklist (Inspections) in a specified Project grouped by a specified attribute,' giving a specific verb and resource. It also distinguishes this tool from siblings by noting its deprecated status and its use for discovery/id lookup before calling other tools.

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

Usage Guidelines5/5

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

Explicitly tells when to use: 'Use this to discover checklists or to look up the id of one before calling a tool that needs it.' It also tells when not to use: 'DEPRECATED... prefer a newer version... use procore_search_endpoints to find it.'

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