Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Company Action Plan Template References

list_company_action_plan_template_references
Read-onlyIdempotent

Retrieve a paginated list of company action plan template references. Use filters to narrow by ID, dates, or template, and control pagination to find specific references.

Instructions

List of all Company Action Plan Template References. Use this to enumerate Action Plans when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Action Plans. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id. Procore API: Project Management > Action Plans. Endpoint: GET /rest/v1.0/companies/{company_id}/action_plans/plan_template_references

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
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__idNoQuery string parameter — return item(s) with the specified IDs.
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__plan_template_item_idNoQuery string parameter — return item(s) associated with the specified Action Plan Template Item ID(s).
filters__plan_template_idNoQuery string parameter — return item(s) associated with the specified Action Plan Template ID.
sortNoQuery string parameter — direction (asc/desc) can be controlled by the presence or absence of '-' before the sort parameter.
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, etc. The description adds that it returns a paginated JSON array with metadata. No contradictions, but no additional behavioral disclosure beyond standard pagination.

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 two sentences plus endpoint details. It is front-loaded with purpose and usage, making it efficient. Slightly longer due to endpoint reference but still 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?

With no output schema, the description covers return format (paginated JSON array, metadata) and key usage. It includes required parameter and filtering options. Reasonably complete for a list tool.

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 coverage is 100%, so the description adds little beyond mentioning page/per_page for pagination and company_id as required. This is baseline value for a fully described schema.

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 lists Company Action Plan Template References and explains its use for enumeration, finding IDs, and filtering. It is specific and differentiates from sibling tools by naming the exact 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 mentions when to use the tool (enumerate, find IDs, filter) and states required parameters. However, it does not explicitly exclude scenarios or mention alternatives, leaving some ambiguity.

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