Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Checklist (Inspection) Schedules

list_checklist_inspection_schedules
Read-onlyIdempotent

Get a paginated list of inspection schedules for a project, filterable by type, location, assignee, due dates, and equipment.

Instructions

Returns the Checklist Schedules from Checklists (Inspections) on the Project. 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}/checklist/schedules

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
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__inspection_type_idNoQuery string parameter — return schedule(s) with the specified Checklist Type IDs
filters__frequencyNoQuery string parameter — return schedule(s) with the specified Frequency Types
filters__location_idNoQuery string parameter — return schedule(s) with the specified Location IDs
filters__list_template_idNoQuery string parameter — return schedule(s) with the specified Inspection Template IDs
filters__assignee_idNoQuery string parameter — return schedule(s) with the specified Assignee IDs
filters__first_inspection_due_atNoQuery string parameter — return schedule(s) with the specified First Inspection Due Date
filters__ends_atNoQuery string parameter — return schedule(s) with the specified Last Inspection Due Date.
filters__endedNoQuery string parameter — return schedule(s) that are finished when true, returns unfinished schedule(s) otherwise
filters__equipment_idNoQuery string parameter — return schedule(s) with the specified Equipment IDs
sortNoQuery string parameter — sort schedule(s) by the chosen param; check below for a list of options. The direction of sorting is ascending by default; for descending sort, insert the - symbol before the param.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
Behavior5/5

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

Annotations already indicate readOnly and idempotent behavior. The description adds that the response is a paginated JSON array with pagination metadata, and provides the exact Procore API endpoint and resource path. This provides clear behavioral context beyond the 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?

The description is concise, front-loading the purpose and usage, then providing additional details about pagination and API endpoint. Every sentence contributes value with no 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?

No output schema is present, but the description states the return is a paginated JSON array with pagination metadata. The filter parameters give hints about item structure. It could be more explicit about the fields of each schedule item, but overall it is fairly complete for a list endpoint.

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 does not add significant meaning beyond what the schema already provides for parameters. It mentions pagination parameters briefly but not more deeply.

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 it returns Checklist Schedules (Inspections) on the project, and provides specific use cases: enumerating inspections for paginated overview, finding IDs, or filtering. It distinguishes itself from the many sibling list tools by explicitly naming the resource.

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 advises when to use the tool (enumerate inspections, paginated overview, filter). It mentions required parameter project_id and pagination controls. However, it does not explicitly state when not to use it or point to alternative tools among the vast sibling set.

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