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

ghl-mcp-server-v2

by zackscriven

ghl_conversation_ai_list_actions

Read-onlyIdempotent

Lists an AI agent's conversation actions, including custom API Call actions, by agent ID. Use it to inspect or audit actions configured for a specific agent.

Instructions

[DEPRECATED per official docs — prefer the documented replacement if one exists.] List Actions for an Agent Deprecated — use GET /conversation-ai/agents/{agentId}/actions instead. List for actions for an agent, including any customApi ("API Call") actions. Endpoint: GET /conversation-ai/agents/{agentId}/actions/list (Version header: v3; source: v3/conversation-ai-v3.json) OAuth scopes: conversation-ai.readonly

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>"
    },
    "name": "ghl_conversation_ai_list_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentIdYesThe unique identifier of the AI agent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • 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.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior; the description adds useful context including the `conversation-ai.readonly` OAuth scope, API version/source, and deprecation status. It does not describe return shape or pagination, but that is a minor gap for a deprecated read-only list endpoint.

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 description is compact and front-loads the deprecation warning with endpoint and auth metadata. It is slightly redundant by repeating the deprecation notice twice and includes a small typo, "List for actions," but remains efficient overall.

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 simple one-parameter tool with rich annotations and no output schema, the description covers purpose, deprecation/replacement, endpoint, OAuth scope, and customApi inclusion. It lacks return-value detail, but the tool's simplicity and the schema/annotation coverage make this mostly complete.

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% for the single `agentId` parameter, and the description only repeats `{agentId}` in the endpoint path. It adds no meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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?

States a specific verb and resource: "List Actions for an Agent," with scope clarified as including any `customApi` ("API Call") actions. It distinguishes the list operation from create/update/delete action siblings, though it does not name the closest replacement MCP sibling directly.

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 marks the tool as deprecated and says to use `GET /conversation-ai/agents/{agentId}/actions` instead, giving a strong when-not-to-use signal. It stops short of naming the corresponding sibling MCP tool such as `ghl_conversation_ai_get_agent_actions`.

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