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

ghl-mcp-server-v2

by zackscriven

ghl_agent_studio_list

Read-onlyIdempotent

Lists active agents for a specified location with limit/offset pagination, and optionally filters results to only published production agents.

Instructions

Lists agents (paginated via limit/offset) — not a get-by-id lookup. List Agents Lists all active agents for the specified location. locationId is required parameter to ensure optimal performance. Supports pagination using limit and offset. Optionally filter by isPublished=true to return only agents with a published production version. Endpoint: GET /agent-studio/agent (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"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitYesMaximum number of agents to return (pagination page size)
offsetYesNumber of agents to skip before collecting results (pagination offset)
sourceNoOrigin channel attributed to this read for auditing (e.g. public_api, internal)
locationIdYesLocation (sub-account) ID to list agents for
isPublishedNoOptional filter to return only agents with a published production version

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.0
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of agents to return (pagination page size)"
    • addedInput schema / properties / locationId / description
      Added value: +"Location (sub-account) ID to list agents for"
    • 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/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds real operational context beyond them: sub-account token requirement, OAuth scope agent-studio.readonly, endpoint path and version header. It stops short of describing return shape or rate limits, so it's strong but not exhaustive.

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?

Load-bearing facts come first and the endpoint/auth lines are useful, but pagination is stated three separate times (opening parenthetical, body sentence, trailing "Pagination params" line) and the title is duplicated inside the body. Noticeable 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 read-only list with no output schema, the description covers auth, scope, filtering and paging well enough to call correctly. It omits what a result item looks like and whether total counts are returned, which an agent may still wonder about.

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 limit/offset/locationId/isPublished are already documented. The description adds only the rationale that locationId is required "to ensure optimal performance" and restates the pagination intent; the `source` auditing parameter is not addressed at all. Baseline 3 fits.

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?

Opens with a specific verb+resource ("Lists agents") and immediately scopes it against the nearest sibling by stating "not a get-by-id lookup." The scope (active agents for a location, optional isPublished filter) is concrete enough to select the tool without opening the schema.

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 rules out the get-by-id case and points at the required location token as the precondition. It doesn't name ghl_agent_studio_get_by_id outright or mention the deprecated list variant, but the when-to-use signal is clear.

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