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

ghl-mcp-server-v2

by zackscriven

ghl_link_update

Idempotent

Update an existing trigger link's display name and redirect URL by supplying its link ID and revised link details.

Instructions

Update Link Endpoint: PUT /links/{linkId} (Version header: v3; source: v3/links-v3.json) OAuth scopes: links.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": {
      "linkId": "<linkId>",
      "body": "<body>"
    },
    "name": "ghl_link_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
linkIdYesLink Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"LinkUpdateDto"
  2. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful operational context the annotations lack: the required links.write OAuth scope and the v3 version header/spec source. It does not disclose whether the update replaces or merges the existing link record, which matters because the body requires both name and redirectTo.

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?

Three short lines, front-loaded with the action, followed by endpoint and auth metadata. Nothing is padded, though the 'source: v3/links-v3.json' provenance note is of marginal value to an invoking agent.

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

Completeness3/5

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

For a two-parameter mutation with a nested request body and no output schema, the definition covers the endpoint, version, and scope but omits what the call returns and whether the update is a full replace or partial patch. Annotations carry the safety and idempotency story, so the remaining gap is moderate rather than severe.

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%, with both linkId and the nested body fields (name, redirectTo) documented and exemplified in the schema itself. The description adds no parameter-level meaning beyond naming the linkId path variable in the endpoint template, 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?

The description gives a specific verb+resource ('Update Link') and reinforces it with the concrete endpoint PUT /links/{linkId}, so an agent knows exactly which resource is mutated. It does not explicitly contrast itself with siblings like ghl_link_create, ghl_link_delete, or ghl_link_get_by_id, but the update semantics are unambiguous from the name and endpoint.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus ghl_link_create, ghl_link_get_by_id, or ghl_link_search_trigger, and no prerequisites beyond the OAuth scope line. The agent must infer usage entirely from the tool name and endpoint.

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