Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete A Single Project

delete_a_single_project
DestructiveIdempotent

Permanently delete a project from a company using its unique company and project IDs. This action cannot be undone.

Instructions

Delete a single project given a company ID and project ID. When a Project has been successfully deleted, you will receive the Project's ID back as confirmation. Use this to permanently delete the specified Resource Planning records. This cannot be undone. Permanently removes the specified Resource Planning records. This action cannot be undone. Required parameters: company_id, project_id. Procore API: Resource Management > Resource Planning. Endpoint: DELETE /rest/v1.0/workforce-planning/v2/companies/{company_id}/projects/{project_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company. This parameter accepts both formats: - **Recommended**: Procore company ID (integer) - Use this for new integrations - Legacy: LaborChart UUID format (uuid string...
project_idYesURL path parameter — unique identifier for the project
Behavior3/5

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

Description adds confirmation response and irreversibility beyond annotations. But does not disclose cascading deletes or authorization requirements. Annotations cover safety profile.

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?

Description is short but contains redundant phrases ('cannot be undone' twice). Front-loaded well but could be trimmed.

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?

Covers confirmation response and endpoint but lacks error conditions, prerequisites, or data scope of deletion. Adequate for simple operation.

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 description only restates required parameters without adding new meaning. Baseline 3 applies.

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?

Clearly states delete action on project resource with company/project IDs. Redundant emphasis on irreversibility but purpose is unambiguous.

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. sibling delete tools or under what conditions (e.g., project must not have active records). Missing when-not-to-use information.

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