Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete A Link

delete_a_link
DestructiveIdempotent

Permanently remove a specific project link from a Procore project. Use this to delete a link record; this action cannot be undone.

Instructions

Send a specific Project Home Link to the recycle bin. Use this to permanently delete the specified Project records. This cannot be undone. Permanently removes the specified Project records. This action cannot be undone. Required parameters: company_id, project_id, id. Procore API (v2.0): Core > Project. Endpoint: DELETE /rest/v2.0/companies/{company_id}/projects/{project_id}/links/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — link unique identifier
Behavior4/5

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

The description adds behavioral context beyond annotations, stating the operation is permanent and sends to recycle bin. Annotations already indicate destructiveHint and idempotentHint, so the description complements rather than contradicts.

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., 'This cannot be undone' repeated twice, identical sentences about permanent deletion). While front-loaded, it could be more concise.

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?

For a simple delete tool, the description covers the action, required parameters, and endpoint. However, it omits expected response or side effects like cascade deletes, which would be helpful given no output schema.

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 the schema fully documents parameters. The description lists required parameters but adds no additional semantics beyond what the schema provides.

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 the action (send to recycle bin, permanently delete) and the resource (Project Home Link). It distinguishes from siblings by specifying 'Project Home Link' but does not explicitly contrast with other link delete tools like 'delete_link'.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or when not to use it.

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