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

ghl-mcp-server-v2

by zackscriven

ghl_funnel_create_redirect

Creates a new URL redirect for a sub-account using domain, path, target, and action to route traffic to a funnel, website, or URL.

Instructions

Create Redirect The "Create Redirect" API Allows adding a new url redirect to the system. Use this endpoint to create a url redirect with the specified details. Ensure that the required information is provided in the request payload. Endpoint: POST /funnels/lookup/redirect (Version header: v3; source: v3/funnels-v3.json) Requires a Sub-Account (location) token. OAuth scopes: funnels/redirect.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_funnel_create_redirect"
  }
}

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: +"CreateRedirectParams"
  2. First observedv2.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the required OAuth scope (funnels/redirect.write) and the location-token requirement. It says nothing, however, about what happens when a redirect already exists for the same domain/path — the most likely failure mode for a non-idempotent create.

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?

The opening repeats the title verbatim ('Create Redirect' ... 'The "Create Redirect" API Allows adding a new url redirect') before delivering any new information. The endpoint/version/scope footer is compact and useful, but the first two sentences are largely padding.

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?

Auth scope, location-token requirement, HTTP endpoint and API version are all present, which is solid for a mutation tool with no output schema. Missing is any statement about the response (e.g. created redirect ID) or duplicate-path behavior, leaving the agent without a complete picture of the call's outcome.

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% and the nested body schema documents all five required fields (locationId, domain, path, target, action) with examples. The description only says to provide the required information in the payload, adding no meaning about field semantics such as how 'action' interacts with 'target' or how path must be formatted.

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 states a specific verb and resource: creating a new URL redirect via POST /funnels/lookup/redirect. It distinguishes itself naturally from the CRUD siblings (update_redirect_by_id, delete_redirect_by_id, fetch_redirects_list) by naming the create action, though it never explicitly references those siblings.

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?

'Use this endpoint to create a url redirect with the specified details' only restates the purpose rather than giving conditions for choosing it over update/fetch siblings. The one genuinely useful usage constraint is the prerequisite that a Sub-Account (location) token is required, which tells the agent what credential context must already be in place.

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