Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Project Punch Item Templates

list_project_punch_item_templates
Read-onlyIdempotent

Retrieve a paginated list of punch item templates for a project. Use filters to find specific templates by ID, active status, or update date.

Instructions

Return a list of all Project Punch Item Templates associated with a Project. Use this to enumerate Punch List records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Punch List records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Project Management > Punch List. Endpoint: GET /rest/v1.0/projects/{project_id}/punch_item_templates

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
filters__idNoQuery string parameter — return item(s) with the specified IDs.
filters__activeNoQuery string parameter — if true, returns item(s) with a status of 'active'.
filters__updated_atNoQuery string parameter — return item(s) within a specific updated at iso8601 datetime range
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number 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 declare readOnlyHint and idempotentHint. Description adds value by specifying paginated JSON array with metadata, explaining pagination control (page, per_page), and noting required parameters. No contradictions with 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?

Description is concise (4-5 sentences) and front-loaded with purpose. Each sentence adds value: lists use cases, mentions pagination, required parameter, and API details. No fluff.

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?

For a list tool with 6 parameters (1 required) and no output schema, the description clearly covers return type (paginated JSON array with metadata), pagination behavior, use cases, and required parameter. No important gaps.

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

Parameters4/5

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

Schema coverage is 100%. Description adds context for pagination parameters (page and per_page) and states that response includes pagination metadata, which goes beyond the schema's basic descriptions. Provides practical usage guidance.

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?

Description explicitly states it returns a list of project punch item templates, with a clear verb ('Return') and resource ('Project Punch Item Templates'). It also specifies use cases (paginated overview, finding IDs, filtering), distinguishing it from sibling 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?

Clearly describes when to use (for enumeration, finding IDs, filtering with query parameters). Provides pagination instructions and references Procore API. However, does not explicitly mention when not to use or compare with alternative tools, which is a minor gap.

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