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

ghl-mcp-server-v2

by zackscriven

ghl_funnel_get_pages_count_by_id

Read-onlyIdempotent

Fetches the count of funnel pages for a given funnel ID and location ID, enabling you to determine the total number of pages in a funnel.

Instructions

Fetch count of funnel pages Retrieves count of all funnel pages based on the given query parameters. Endpoint: GET /funnels/page/count (Version header: v3; source: v3/funnels-v3.json) Requires a Sub-Account (location) token.

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>"
    },
    "name": "ghl_funnel_get_pages_count_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
funnelIdYes
locationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/5.0
Behavior4/5

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

Adds context beyond the annotations: the exact endpoint, the v3 version header, and the auth requirement (Sub-Account / location token). That auth note is genuinely useful and is not derivable from the readOnly/idempotent hints. It stops short of saying the count is scoped per funnel or per location.

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 first two lines are redundant restatements of the same fact ('Fetch count of funnel pages' / 'Retrieves count of all funnel pages'), while the actually useful details (endpoint, auth) are pushed to the end. Front-loading is weak and one sentence could be removed with no loss.

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 simple read-only counting tool with clear annotations, the description is close to sufficient, but with no output schema and 0% schema parameter coverage, the agent still cannot tell what the returned count covers or how funnelId/locationId/name affect it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description needs to carry the parameter burden, but it only says 'based on the given query parameters' without identifying name, funnelId, or locationId. It never explains that funnelId scopes the count or that name optionally filters pages.

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 (fetch count) and resource (funnel pages), and the endpoint path confirms it is a count-only read against /funnels/page/count. It does not explicitly differentiate itself from the closely named sibling ghl_funnel_get_pages_by_id, which returns the pages themselves rather than a count.

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 by the word 'count' – an agent must infer that this is the cheap alternative to ghl_funnel_get_pages_by_id when only a total is needed. No when-to-use, when-not-to-use, or alternative is named.

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