Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

List Checklist Templates (Deprecated)

list_checklist_templates
Read-onlyIdempotent

Retrieve Inspection Checklist Templates for a specified project to discover available templates or find a template ID for use in other Procore API calls.

Instructions

Returns a list of all Inspection Checklist Templates for a specified Project. DEPRECATED: Procore has deprecated this endpoint (as of 2022-01-27). 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 checklist templates or to look up the id of one before calling a tool that needs it. Returns a JSON array of checklist templates; 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/list_templates

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
project_idYesQuery string parameter — unique identifier for the project.

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

The description discloses pagination behavior ('page and per_page control pagination and the response reports how many pages remain'), error payload patterns (401, 403, 404), and confirms read-only nature. This adds value beyond the annotations, which already mark it as read-only and non-destructive. No contradictions.

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 well-structured, front-loaded with purpose, then deprecation, use case, return type, pagination, safety, errors, and API reference. Every sentence contributes valuable information without redundancy.

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

Completeness5/5

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

The description is thorough for a list tool: it covers purpose, deprecation and alternatives, usage guidance, pagination, read-only nature, error conditions, and the required parameter. Given no output schema, it adequately states the return type (JSON array).

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 descriptions cover 100% of parameters, so the baseline is 3. The description mentions project_id as required and page/per_page for pagination, but does not add 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 tool returns a list of all Inspection Checklist Templates for a specified project, with a specific verb ('Returns') and resource. It also notes deprecation and the use case of looking up IDs before other calls, distinguishing it from newer alternatives.

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 warns the endpoint is deprecated and instructs to prefer a newer version, directing users to procore_search_endpoints. It also states when to use this tool (to discover templates or look up an ID), providing clear usage context and an alternative.

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