Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Company Folder

delete_company_folder
DestructiveIdempotent

Permanently delete a company folder and its documents. This action cannot be undone.

Instructions

Delete the specified Folder by moving it to the recycle bin. Use this to permanently delete the specified Documents. This cannot be undone. Permanently removes the specified Documents. This action cannot be undone. Required parameters: company_id, id. Procore API: Core > Documents. Endpoint: DELETE /rest/v1.0/companies/{company_id}/folders/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
idYesURL path parameter — unique identifier of the Documents resource
Behavior2/5

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

The description contains contradictory statements: 'move to recycle bin' vs 'permanently delete' and 'cannot be undone'. Annotations provide destructiveHint=true, but the description fails to clarify the actual behavior (e.g., restorability).

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 short but contains repetition ('This cannot be undone' twice, 'Permanently removes the specified Documents' twice). It includes API endpoint info which is helpful but could be more focused.

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?

For a simple delete tool with two params and no output schema, the description should clarify behavior (recycle bin vs permanent), effects on contents, and restorability. The contradictory statements leave the agent uncertain.

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%, and the description merely restates the required parameters without adding new meaning. The schema already explains company_id and id as URL path parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the verb 'Delete' and the resource 'Folder', but it confuses by mentioning 'permanently delete the specified Documents' instead of Folder. This ambiguity reduces clarity, though the title helps slightly.

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 tool versus alternative folder deletion tools or other delete operations. The description only warns 'cannot be undone' but does not provide context or exclusions.

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