Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Recycled Action Plan Section

show_recycled_action_plan_section
Read-onlyIdempotent

Retrieve full details of a recycled action plan section by project ID and section ID. Returns a JSON object with the requested section data.

Instructions

Show Recycled Action Plan Section. 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_sections/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — action Plan Section ID
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description's read operation aligns but adds little beyond confirming fetch behavior. Includes API endpoint context, which adds marginal value.

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?

Concise, front-loaded with purpose. Endpoint detail is extra but not wasteful. Good structure.

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?

No output schema, description only vaguely states 'Returns a JSON object'. For a simple get operation, this is adequate but could be more specific about return shape.

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 baseline 3. Description mentions required parameters and endpoint but does not add significant meaning beyond schema descriptions.

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 fetches full details of a specific action plan section by identifier, with required parameters. Minor inconsistency: mentions 'Action Plans' plural but tool is for a single section. Overall specific verb+resource.

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

Usage Guidelines2/5

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

No guidance on when to use this vs alternatives (many similar show_recycled_* tools). No exclusions or context 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