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

ghl-mcp-server-v2

by zackscriven

ghl_funnel_get_pages_by_id

Read-onlyIdempotent

Retrieve all pages for a specific funnel by funnel ID and location, using limit and offset to paginate through full results.

Instructions

Fetch list of funnel pages Retrieves a list of all funnel pages based on the given query parameters. Endpoint: GET /funnels/page (Version header: v3; source: v3/funnels-v3.json) Requires a Sub-Account (location) token. Pagination params: limit, offset — pass them to page through full result sets.

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": {
      "locationId": "<locationId>",
      "funnelId": "<funnelId>",
      "limit": "<limit>",
      "offset": "<offset>"
    },
    "name": "ghl_funnel_get_pages_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
limitYes
offsetYes
funnelIdYes
locationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/destructive semantics, and the description adds real context beyond that: it requires a Sub-Account (location) token and explains that limit/offset must be passed to page through full result sets. It stops short of describing the return shape or default page size.

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?

Front-loads the core action and keeps endpoint/metadata on dedicated lines. The first two lines are slightly redundant (title line then 'Retrieves a list...'), but overall it is well-structured with minimal waste.

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 five-parameter, four-required list tool with zero schema description coverage and no output schema, the description covers pagination and auth but leaves funnelId, name filtering, and return behavior unexplained. It is adequate but has clear gaps an agent would need to infer.

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 0%, so the description must carry parameter meaning. It explains limit/offset (pagination) and hints at locationId via the token note, but leaves funnelId and the name filter completely unexplained across five parameters, leaving a meaningful gap.

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+resource combination ('Fetch list of funnel pages') that an agent can immediately understand. It doesn't distinguish itself from the sibling ghl_funnel_get_pages_count_by_id or ghl_funnel_list, so it stops short of full clarity against alternatives.

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 the count sibling or the funnel list sibling, and no prerequisites beyond a token requirement. 'Based on the given query parameters' offers no routing 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