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

ghl-mcp-server-v2

by zackscriven

ghl_agent_studio_list_deprecated

Read-onlyIdempotent

Lists active agents with published production versions for a specified location via a deprecated endpoint, supporting limit and offset pagination; prefer the documented replacement.

Instructions

Deprecated per official spec — use ghl_agent_studio_list (GET /agent-studio/agent) instead. [DEPRECATED per official docs — prefer the documented replacement if one exists.] List Agents (Deprecated) Deprecated endpoint - use GET /agent instead.

Lists all active agents that have a published production version for the specified location. locationId is required parameter. Supports pagination using limit and offset. Endpoint: GET /agent-studio/public-api/agents (Version header: v3; source: v3/agent-studio-v3.json) Requires a Sub-Account (location) token. OAuth scopes: agent-studio.readonly Pagination params: limit, offset — pass them to page through full result sets.

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>",
      "limit": "<limit>",
      "offset": "<offset>"
    },
    "name": "ghl_agent_studio_list_deprecated"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitYesPage size (default 20, max 100)
offsetYesNumber of agents to skip before collecting results (pagination offset)
sourceNoOrigin channel attributed to this read for auditing (e.g. public_api, internal)
locationIdYesLocation ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.0
    • addedInput schema / properties / limit / description
      Added value: +"Page size (default 20, max 100)"
    • addedInput schema / properties / locationId / description
      Added value: +"Location ID"
    • addedInput schema / properties / offset / description
      Added value: +"Number of agents to skip before collecting results (pagination offset)"
    • addedInput schema / properties / source / description
      Added value: +"Origin channel attributed to this read for auditing (e.g. public_api, internal)"
  2. First observedv2.0.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly and idempotent annotations, the description discloses the required Sub-Account token, the OAuth scope agent-studio.readonly, the fixed endpoint and version header, and that only active agents with a published production version are returned. These are substantive operational details that annotations alone do not provide.

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?

The same deprecation warning is repeated in multiple forms: an opening line, a bracketed note, the title, and a bolded sentence. Those redundant lines and the duplicated title waste space, though the actual usage details remain front-loaded.

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 list endpoint, the description covers the endpoint, required auth, scope, active/published filtering, and pagination. It does not describe the return shape, and no output schema exists, but the tool's output is reasonably inferable from the stated purpose.

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 the schema already explains locationId, limit, offset, and source. The description reinforces that locationId is required and that limit/offset page through full result sets, but it adds no syntax or format details beyond the schema's own parameter descriptions.

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?

The description names a specific resource and scope: all active agents with a published production version for a given location. It also identifies the exact replacement tool, ghl_agent_studio_list, making the deprecated status unambiguous and distinguishing it from its sibling.

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

Usage Guidelines5/5

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

It explicitly says this endpoint is deprecated and directs the agent to use ghl_agent_studio_list instead. That gives a clear when-not-to-use condition and names the alternative, leaving no inference needed.

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