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

ghl-mcp-server-v2

by zackscriven

ghl_agent_studio_update_version

Update a specific agent version's nodes, edges, variables, and configuration by versionId to modify its workflow or settings.

Instructions

Update Agent Updates a specific agent version by versionId. Supports updating nodes, edges, variables, and configuration. Endpoint: PATCH /agent-studio/agent/versions/{versionId} (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": {
      "versionId": "<versionId>",
      "body": "<body>"
    },
    "name": "ghl_agent_studio_update_version"
  }
}

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)
versionIdYesAgent version ID to update

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"UpdatePublicAgentVersionDTO"
    • addedInput schema / properties / source / description
      Added value: +"Origin channel attributed to this write for auditing (e.g. public_api, internal)"
    • addedInput schema / properties / versionId / description
      Added value: +"Agent version ID to update"
  2. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

The description adds real value beyond the annotations by disclosing the HTTP verb/path and the auth model (sub-account token, agent-studio.write scope). However, it omits the most consequential behavior for a PATCH with idempotentHint=false: that nodes/edges must be supplied as complete arrays, which lives only in the schema, and it says nothing about reversibility or side effects.

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?

Four compact lines with the behavior first and endpoint/auth metadata trailing, so the actionable content is front-loaded. The redundant 'Update Agent' leading line duplicates the title and earns nothing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nested-body mutation with no output schema and full parameter documentation, the description covers endpoint, auth, and scope - the pieces the schema cannot express. The gaps that remain (full-array replacement, side effects) are documented in the schema itself.

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 baseline is 3. The description's mention of versionId, nodes, edges, variables and configuration mirrors what the schema already documents in far greater detail, adding no new semantics such as partial-vs-full replacement rules.

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 ('Updates a specific agent version by versionId') and names the field groups affected (nodes, edges, variables, configuration). It does not distinguish itself from the sibling ghl_agent_studio_update_metadata or ghl_agent_studio_promote_and_publish, so the agent must infer which 'update' 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 only implied through the endpoint and auth requirements ('Requires a Sub-Account (location) token', 'OAuth scopes: agent-studio.write'). There is no explicit statement of when to pick this over update_metadata or promote_and_publish, and no prerequisites such as needing an existing version to patch.

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