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

ghl-mcp-server-v2

by zackscriven

ghl_agent_studio_create

Create a new Agent Studio agent with an initial staging version that can later be promoted to production. Provide location ID, status, and version configuration to begin building an agent.

Instructions

Create Agent Creates a new agent with staging version. The agent will be created with an initial staging version that can later be promoted to production. Endpoint: POST /agent-studio/agent (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": {
      "body": "<body>"
    },
    "name": "ghl_agent_studio_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
sourceNoOrigin channel attributed to this write for auditing (e.g. public_api, internal)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"CreatePublicAgentDTO"
    • 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.8/5.0
Behavior4/5

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

Beyond the annotations (which already mark this as a non-idempotent, non-destructive write), the description discloses the endpoint, API version header, required token type, and OAuth scope. It also clarifies the important behavioral fact that the newly created agent is not live but in staging. It stops short of describing the response or what happens on duplicate names.

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

Conciseness5/5

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

The purpose is front-loaded in the first line, followed by the staging-lifecycle detail and then compact operational metadata (endpoint, version, token, scope). The only mild redundancy is restating the title in the opening line, but nothing is wasted.

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 create call with a deeply nested request body, the description covers auth, scope, endpoint and the staging-vs-production semantic, and the schema documents the body fully, so no output schema is needed. The remaining gap is that it does not say what identifier or payload comes back after creation.

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% and every body field carries its own description and examples, so the description is not required to compensate. It adds no field-level meaning of its own, so the baseline 3 applies.

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 ("Creates a new agent") and adds the key scope detail that the agent is created with an initial staging version rather than live. It does not explicitly distinguish itself from similar create tools in the same family (ghl_conversation_ai_create_agent, ghl_voice_ai_create_agent), so the sibling differentiation is only implicit through the name.

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?

The description implies the lifecycle context (a staging version that can later be promoted to production), which hints at when this is the right entry point, but it never names the promotion tool or says when to prefer a different create tool. Auth prerequisites (sub-account token, agent-studio.write scope) are stated, which is genuinely useful 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