Skip to main content
Glama
TylerIlunga

Procore MCP Server

Delete Project Region

delete_project_region
DestructiveIdempotent

Permanently delete a project region from company settings using company ID and region ID. This action cannot be undone.

Instructions

Delete the specified Project Region. Use this to permanently delete the specified Company Settings. This cannot be undone. Permanently removes the specified Company Settings. This action cannot be undone. Required parameters: company_id, id. Procore API: Company Admin > Company Settings. Endpoint: DELETE /rest/v1.0/companies/{company_id}/project_regions/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
idYesURL path parameter — iD of the Project Region
Behavior3/5

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

Annotations already indicate destructive behavior. Description reinforces with 'cannot be undone' and adds endpoint detail. No new behavioral traits beyond annotations, but consistent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Repetitive phrasing ('cannot be undone', 'Permanently removes' said twice) makes it less concise. Could be trimmed to a single sentence.

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?

No output schema, and description doesn't explain response or side effects beyond deletion. For a destructive tool, more context on implications would be helpful.

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 covers both parameters with descriptions (100% coverage). Description only mentions required parameters without adding extra meaning.

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 deletion of a specific resource (Project Region). However, it mentions 'Company Settings' inconsistently, which may cause slight confusion. It differentiates from sibling delete tools by specifying the exact resource type.

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 explicit guidance on when to use vs alternatives. Merely states 'Use this to permanently delete...' but lacks when-to-use or when-not-to-use context.

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