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

ghl-mcp-server-v2

by zackscriven

ghl_conversation_ai_delete_action

DestructiveIdempotent

Permanently deletes a Conversation AI agent action, including classic and API Call actions, by action and agent IDs; removal applies to all associated agents and cannot be undone.

Instructions

Remove Action from Agent Permanently deletes an action. This will remove the action from all associated agents and cannot be undone. Applies to both classic and customApi ("API Call") actions. Endpoint: DELETE /conversation-ai/agents/{agentId}/actions/{actionId} (Version header: v3; source: v3/conversation-ai-v3.json) OAuth scopes: conversation-ai.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": {
      "actionId": "<actionId>",
      "agentId": "<agentId>"
    },
    "name": "ghl_conversation_ai_delete_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentIdYesThe unique identifier of the AI agent
actionIdYesThe unique identifier of the action ID Attached to the agent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • addedInput schema / properties / actionId / example
      Added value: +"6578278e879ad2646715ba9c"
    • addedInput schema / properties / agentId / description
      Added value: +"The unique identifier of the AI agent"
    • addedInput schema / properties / agentId / example
      Added value: +"ve9EPM428h8vShlRW1KT"
  2. First observedv2.0.0

TDQS

A3.7/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 genuinely new behavioral context: the blast radius ("remove the action from all associated agents"), the irreversibility ("cannot be undone"), and the required `conversation-ai.write` OAuth scope. It does not cover failure behavior (e.g., unknown actionId), which keeps it short of a 5.

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?

The destructive effect and irreversibility are front-loaded in the first two lines, with endpoint and scope metadata appended as a reference footer. The opening line duplicates the annotation title, which is minor waste, but the rest is dense and relevant.

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 definition covers what an agent needs: which IDs are required, that the deletion propagates to all associated agents, that it is unrecoverable, and the required scope. Only the return/confirmation shape is unaddressed, which is a small gap.

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%, so both `agentId` and `actionId` are already documented in the schema. The endpoint template `DELETE /conversation-ai/agents/{agentId}/actions/{actionId}` does imply the parent-child relationship between the two IDs, but no extra format or constraint guidance is offered beyond that, so the baseline of 3 holds.

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?

The description gives a concrete verb and resource ("Permanently deletes an action" on an AI agent) and scopes it to both classic and `customApi` actions. It is clear, but it does not name a discriminating sibling such as `ghl_voice_ai_delete_action` or `ghl_conversation_ai_update_action`, so an agent must infer from naming which deletion surface applies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the condition "Applies to both classic and `customApi` (\"API Call\") actions" narrows the applicability, and the irreversibility warning signals caution, but there is no explicit when-to-use versus when-to-use-something-else guidance. An agent can infer deletion semantics from the name but gets no routing to `update_action`/`delete_agent` alternatives.

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