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

ghl-mcp-server-v2

by zackscriven

ghl_agent_studio_delete

DestructiveIdempotent

Deletes a GoHighLevel Agent Studio agent and all its versions by agent ID within a sub-account, removing the agent permanently when cleanup is required.

Instructions

Delete Agent Deletes an agent and all its versions. Endpoint: DELETE /agent-studio/agent/{agentId} (Version header: v3; source: v3/agent-studio-v3.json) Requires a Sub-Account (location) token. OAuth scopes: agent-studio.write

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": {
      "agentId": "<agentId>",
      "locationId": "<locationId>"
    },
    "name": "ghl_agent_studio_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceNoOrigin channel attributed to this write for auditing (e.g. public_api, internal)
agentIdYesAgent ID to delete (removes the agent and all its versions)
locationIdYesLocation (sub-account) ID that owns the agent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • addedInput schema / properties / agentId / description
      Added value: +"Agent ID to delete (removes the agent and all its versions)"
    • addedInput schema / properties / locationId / description
      Added value: +"Location (sub-account) ID that owns the agent"
    • addedInput schema / properties / source / description
      Added value: +"Origin channel attributed to this write for auditing (e.g. public_api, internal)"
  2. First observedv2.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real operational context beyond them: the cascade to all versions, the required Sub-Account (location) token, the agent-studio.write OAuth scope, and the exact endpoint and API version. It does not say whether the deletion is permanent or recoverable, which is the one meaningful gap.

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

Conciseness4/5

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

Front-loads the action and its consequence in the first two lines, then tucks endpoint and auth metadata after. Compact overall, though the raw endpoint/version-header/source-file metadata is scaffolding rather than agent-facing guidance.

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 destructive, no-output-schema delete, the definition covers what is destroyed (agent plus versions), the auth model, and the API surface. Irreversibility/restore behavior is the only omission an agent would want before committing.

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 description coverage is 100%, so agentId and locationId are already well documented; the description only loosely reinforces this by framing locationId as a Sub-Account token requirement. The optional 'source' auditing parameter is never mentioned, so the description adds little beyond the schema.

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?

Uses a specific verb and resource (Delete Agent) and states the blast radius: 'Deletes an agent and all its versions.' That is unambiguous against siblings like update_metadata or promote_and_publish, though it never explicitly names which alternative to use when the intent is merely to deactivate or edit.

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 gives no when-to-use / when-not-to-use guidance and names no alternative operation such as updating or deprecating an agent. The only contextual requirement stated is a Sub-Account token and the agent-studio.write scope, which is a prerequisite, not selection guidance.

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