Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Retrieve Recycled Link

retrieve_recycled_link
Idempotent

Restore a deleted Project Home Link from the recycle bin using its unique ID. Specify the project and link ID to retrieve and reactivate the link.

Instructions

Retrieves and restores a specific Project Home Link from the recycle bin. Note: Requires either Company Admin or Project Home Admin permission. Send only the fields you intend to change; omitted fields keep their current values. id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified recycled link on success. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: project_id, id. Procore API: Company Admin > Project-Level Configuration. Endpoint: PATCH /rest/v1.0/links/{id}/restore

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Project-Level Configuration resource
project_idYesQuery string parameter — unique identifier for the project.

Tool Definition Quality

A4.6/5.0
Behavior5/5

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

Discloses partial update behavior ('Send only the fields you intend to change; omitted fields keep their current values'), permission requirements, and detailed failure semantics (401/403/404). This goes well beyond the annotations, which only indicate readOnly=false, idempotent=true, destructive=false.

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 longer than average but every sentence provides value—purpose, permissions, partial update, id resolution, return value, error handling, and endpoint. It is well-structured and front-loaded with the main purpose.

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

Completeness5/5

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

For a mutation/restore operation with no output schema, the description fully covers prerequisites, behavior, return value, and error conditions. It leaves little ambiguity for the agent selecting and invoking the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema already covers both parameters (100%). The description adds crucial meaning for id: 'id must identify an existing parent record — resolve it with the matching list tool first.' This clarifies the id's role beyond the schema's generic description.

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 a specific action: 'Retrieves and restores a specific Project Home Link from the recycle bin.' This distinguishes it from sibling tools like list_recycled_links (which lists) and delete_a_link (which deletes).

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?

It provides clear context: requires specific permissions, must resolve id with a list tool first, and suggests using the matching list tool as a prerequisite. It does not explicitly contrast with all alternatives but offers enough guidance for appropriate use.

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