Skip to main content
Glama
TylerIlunga

Procore MCP Server

list_checklists_inspections

Retrieve and filter inspection checklists from Procore projects to manage compliance and track progress.

Instructions

List Checklists (Inspections). [Project Management/Inspections] GET /rest/v1.0/projects/{project_id}/checklist/lists

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUnique identifier for the project.
pageNoPage
per_pageNoElements per page
filters__idNoReturn item(s) with the specified IDs.
filters__inspection_dateNoReturn item(s) with inspection date within the specified ISO 8601 date range.
filters__inspection_type_idNoArray of Inspection Type IDs. Return item(s) associated with the specified Inspection Type IDs.
filters__inspector_idNoArray of User IDs. Return item(s) where the specified User IDs are inspectors.
filters__template_idNoArray of Checklist Template IDs. Return item(s) associated to the specified Checklist Template IDs.
filters__location_idNoLocation ID. Returns item(s) with the specified Location ID or a range of Location IDs.
filters__managed_equipment_idNoReturn item(s) with the specified Managed Equipment ID.
filters__point_of_contact_idNoArray of User IDs. Return item(s) where the specified User IDs are the point of contact.
filters__spec_section_idNoArray of Specification Section IDs. Return item(s) associated to the specified Specification Section IDs.
filters__responsible_contractor_idNoArray of Vendor IDs. Return item(s) where the specified Vendor IDs are the responsible contractor.
filters__closed_by_idNoArray of User IDs. Return item(s) closed by the specified User ID.
filters__created_by_idNoReturn item(s) created by the specified User IDs
filters__statusNoReturn item(s) with the specified statuses
filters__trade_idNoTrade ID
filters__queryNoReturn item(s) containing search query
filters__due_atNoReturn item(s) due within the specified date range.
filters__created_atNoReturn 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_atNoReturn 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_atNoReturns item(s) closed within the specified ISO 8601 datetime range.
sortNosort
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the action and endpoint, missing critical details like whether it's read-only, pagination behavior, rate limits, authentication requirements, or error handling. This leaves significant gaps in understanding how the tool behaves.

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 concise with two parts: the action and the API endpoint. It is front-loaded with the purpose, and the endpoint provides technical context without unnecessary elaboration. However, the inclusion of the endpoint in brackets adds minor clutter, slightly reducing efficiency.

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

Completeness2/5

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

Given the complexity (23 parameters, no annotations, no output schema), the description is inadequate. It lacks information on return values, pagination, error cases, and operational constraints. For a list tool with many filters, more context is needed to ensure proper usage and interpretation of results.

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 schema already documents all 23 parameters thoroughly. The description adds no additional parameter semantics beyond implying listing with filters via the endpoint. This meets the baseline of 3, as the schema carries the burden, but the description does not enhance parameter understanding.

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 'List Checklists (Inspections)' clearly states the verb ('List') and resource ('Checklists (Inspections)'), indicating it retrieves a collection of checklist inspections. It is specific about the resource type, though it does not explicitly differentiate from sibling tools like 'list_checklists' or 'list_checklist_inspection_schedules' beyond the title.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It mentions the API endpoint but does not specify use cases, prerequisites, or exclusions. Without such context, the agent lacks direction on appropriate invocation scenarios.

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