Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Recycled Company Action Plan Templates

list_recycled_company_action_plan_templates
Read-onlyIdempotent

Retrieve recycled action plan templates for a company with pagination and filtering. Find templates by creation, deletion, or update dates, and by IDs or type.

Instructions

Returns a list of Recycled Company Action Plan Templates for a given company. 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 (v1.1): Project Management > Action Plans. Endpoint: GET /rest/v1.1/companies/{company_id}/recycle_bin/action_plans/plan_templates

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__deleted_atNoQuery string parameter — returns item(s) deleted within the specified ISO 8601 datetime range.
filters__deleted_by_idNoQuery string parameter — return item(s) deleted by the specified User IDs
filters__idNoQuery string parameter — return item(s) with the specified IDs.
filters__type_idNoQuery string parameter — return item(s) with a specific Action Plan Type ID or a range of Action Plan Type 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...
sortNoQuery string parameter — direction (asc/desc) can be controlled by the presence or absence of '-' before the sort parameter.
Behavior4/5

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

Annotations already provide read-only, idempotent, open-world hints. The description adds that it returns a paginated JSON array with metadata and specifies the exact endpoint URL, which enriches understanding without contradicting 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 two sentences plus endpoint info, front-loaded with the main action, and every sentence adds value. No fluff or repetition.

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?

Given the tool's complexity (pagination, filters, recycled scope) and no output schema, the description covers the core aspects. It could mention that it only returns deleted items and note the maximum per_page (in schema), but overall it's adequate.

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?

The schema already covers all 10 parameters in detail (100% coverage). The description only adds that company_id is required and page/per_page control pagination, which is helpful but does not significantly expand on schema explanations.

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 Recycled Company Action Plan Templates for a company, specifies the action (list/enumerate), and distinguishes from siblings like non-recycled templates and recycled action plans via the 'Recycled' and 'Template' qualifiers.

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 tells when to use (for paginated overview, finding IDs, filtering) but does not explicitly mention when not to use or name alternatives, though the recycled context makes it clear vs non-recycled versions.

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