Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Recycled Company Action Plan Template Items Assignees

list_recycled_company_action_plan_template_items_assignees
Read-onlyIdempotent

Retrieve recycled company action plan template item assignees with pagination and filters. Use to recover or audit deleted assignees by company ID.

Instructions

Returns all Recycled Company Action Plan Template Item Assignees 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: Project Management > Action Plans. Endpoint: GET /rest/v1.0/companies/{company_id}/recycle_bin/action_plans/plan_template_item_assignees

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
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__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 section(s) associated with the specified Action Plan Template ID(s).
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...
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
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 declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds pagination behavior (page/per_page, metadata) and mentions filtering, which goes beyond annotations without contradicting them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is reasonably concise but includes extraneous API meta information (Procore API, endpoint). Could be tightened to focus on agent-relevant details.

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

Completeness3/5

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

Covers pagination, filtering, and required params. However, no output schema is provided, and the description inaccurately says it returns 'Action Plans' instead of 'assignees', reducing completeness.

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% with detailed parameter descriptions. The description reinforces that company_id is required and pagination parameters control output, but does not add significant new meaning beyond the schema.

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 clearly states it returns all Recycled Company Action Plan Template Item Assignees for a given company, but inconsistently refers to 'Action Plans' later, which is slightly misleading. The name and title explicitly differentiate this as a recycled, company-level list tool.

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

Usage Guidelines3/5

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

The description advises using it for paginated overviews, finding IDs, or filtering – adequate for a list tool. It does not explicitly contrast with sibling tools like list_action_plan_template_item_assignees, but the 'recycled' and 'company' qualifiers imply context.

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