Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Recycled Action Plan Item

show_recycled_action_plan_item
Read-onlyIdempotent

Retrieve full details of a recycled action plan item from a project's recycle bin. Use project and item IDs to get JSON data for review or restoration.

Instructions

Returns a Specific Recycled Action Plan Item for a given Project. Use this to fetch the full details of a specific Action Plans by its identifier. Returns a JSON object describing the requested Action Plans. Required parameters: project_id, id. Procore API: Project Management > Action Plans. Endpoint: GET /rest/v1.0/projects/{project_id}/recycle_bin/action_plans/plan_items/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — unique identifier of the Action Plans resource
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior2/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 no behavioral context beyond stating it returns a JSON object. It does not disclose pagination behavior despite page/per_page parameters, nor error handling or edge cases.

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 contains redundancy (e.g., repeats 'Returns ... Action Plan Item' and 'fetch full details of a specific Action Plans'). It is not overly long but could be tightened by removing duplicate statements.

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

Completeness2/5

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

No output schema exists, so the description should detail the response structure, but it only says 'Returns a JSON object'. It does not explain the purpose of page/per_page parameters in a show endpoint, nor how to handle errors or empty results. Given the simple read operation, it is minimally adequate but lacks 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%, so each parameter has a description. The description merely restates required parameters without adding new meaning or clarifying the role of optional page/per_page parameters.

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 a specific recycled action plan item for a given project, using required identifiers. It distinguishes from sibling list and other show tools by focusing on a single item.

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 implies usage when you have a specific item identifier, but does not explicitly contrast with list_recycled_action_plan_items or other show tools. No when-not-to-use or alternative guidance is provided.

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