Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Checklists

list_checklists
Read-onlyIdempotent

Retrieve a paginated list of project inspections grouped by template. Use filters such as status, inspector, or location to locate specific checklists.

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. 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/checklist/lists

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesQuery string parameter — unique identifier for the project.
filters__viewNoQuery string parameter — if 'recycle', return deleted Checklists.
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__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 — filters by specific location (Note: Use *either* this or location_id_with_sublocations, but not both)
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__statusNoQuery string parameter — returns item(s) matching the specified status value.
filters__trade_idNoQuery string parameter — filter results by trade id
filters__searchNoQuery string parameter — returns item(s) matching the specified search query string.
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...
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds behavioral context: grouping by attribute, pagination, and pagination metadata. It does not contradict annotations and provides useful details beyond them.

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

Conciseness3/5

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

The description is long but structured. It includes a link, endpoint info, and usage tips. Some redundancy exists (e.g., 'Returns a paginated JSON array of Inspections' is stated both in description and implied by pagination). Could be more concise.

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 tool's complexity (17 parameters, no output schema), the description covers core purpose, grouping, filtering, pagination, and endpoint. It mentions return type and metadata. It is adequate but does not explain all parameter details (schema covers them).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. However, the description claims grouping 'by a specified attribute' but the input schema has no such parameter, which is misleading. The description adds little parameter-specific meaning beyond what the schema already provides.

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 the verb (Lists), the resource (Checklist/Inspections) and its scope (in a specified Project, grouped by a specified attribute). It distinguishes the tool by mentioning grouping and filtering, which sets it apart from other list tools.

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?

The description explicitly tells when to use the tool: 'to enumerate Inspections when you need a paginated overview, to find IDs, or to filter by query parameters.' It does not state when not to use or compare with alternatives, but the context is clear.

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