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

ghl-mcp-server-v2

by zackscriven

ghl_link_create

Creates a trigger link for a business location with a display name and redirect URL, so clicks can send users to a target page or variable.

Instructions

Create Link Endpoint: POST /links/ (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": {
      "body": "<body>"
    },
    "name": "ghl_link_create"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare non-read-only, open-world, non-idempotent and non-destructive, so the safety profile is covered. The description adds the required OAuth scope 'links.write' and the v3 version header, which is genuinely useful auth context an agent cannot get from annotations. It adds nothing beyond that — no note on side effects, uniqueness constraints, or whether duplicate names are allowed.

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, then endpoint and auth. Dense and waste-free, though the 'source: v3/links-v3.json' provenance note is internal metadata of little use to an agent selecting or calling the tool.

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?

There is no output schema, and the description never says what the call returns — an agent needs the created link's ID to subsequently get, update or delete it, and that is not stated. Body shape is fully documented by the nested schema, so the main remaining gap is the return value.

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 per-field descriptions for name, locationId and redirectTo, including examples, so the schema carries parameter documentation. The description contributes no additional parameter meaning, which is acceptable at this coverage level.

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 ('Create Link') plus the exact endpoint POST /links/, which distinguishes it from ghl_link_update, ghl_link_get_by_id, ghl_link_list and ghl_link_search_trigger. It does not explain what a 'link' is in this product context, but the operation itself is unambiguous.

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?

Creation is implied usage and no alternatives are named, though none are strictly confused here since siblings have distinct verbs. There is no guidance on prerequisites (e.g. that locationId must reference an existing location) or on when a link should be created versus updated.

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