Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_location_delete

DestructiveIdempotent

Permanently deletes a sub-account (formerly location) from an agency; requires an agency-level token and lets you also remove its linked Twilio sub-account.

Instructions

REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only. Irreversible: deletes the sub-account; deleteTwilioAccount query param controls whether the attached Twilio sub-account is also torn down. Delete Sub-Account (Formerly Location) Delete a Sub-Account (Formerly Location) from the Agency Endpoint: DELETE /locations/{locationId} (Version header: v3; source: v3/locations-v3.json) Requires an Agency (company-level) token. OAuth scopes: locations.internal-access-only

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "locationId": "<locationId>",
      "deleteTwilioAccount": "<deleteTwilioAccount>"
    },
    "name": "ghl_location_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationIdYesLocation Id
deleteTwilioAccountYesBoolean value to indicate whether to delete Twilio Account or not

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Goes beyond the annotations (destructiveHint, idempotentHint) by disclosing cascade behavior — that deleteTwilioAccount tears down the attached Twilio sub-account — plus the agency-token and OAuth scope requirements. This is genuinely useful context an agent would not get from the structured fields alone.

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 agency-token requirement is stated twice (in the opening line and again as 'Requires an Agency (company-level) token'), and the endpoint/version detail duplicates annotation metadata. Useful content is front-loaded, but there is measurable redundancy.

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

Completeness4/5

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

For a two-parameter destructive tool with no output schema, the description covers the critical safety facts — irreversibility, auth level, cascade side effects, and endpoint. Little an agent needs to invoke it is missing, aside from return-value expectations.

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 coverage is 100%, so the baseline would be 3. The description adds meaning by framing deleteTwilioAccount as controlling whether the attached Twilio sub-account is 'torn down,' clarifying the blast radius of that boolean beyond the schema's generic wording.

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?

States a specific verb and resource ('Delete a Sub-Account (Formerly Location) from the Agency') and names the exact endpoint. This clearly distinguishes it from sibling tools like ghl_location_update, ghl_location_create, and ghl_location_search.

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?

Explicitly states a hard prerequisite (agency/company-level token) and warns of irreversibility, which tells an agent when this is appropriate. It does not, however, name alternatives (e.g. deactivating vs. deleting) or describe when an agent should prefer a different tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools