Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get website funnel

analytics_getWebsiteFunnel
Read-onlyIdempotent

One saved funnel (funnelId from getWebsiteFunnels).

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": {
      "siteId": "<siteId>",
      "funnelId": "<funnelId>"
    },
    "name": "analytics_getWebsiteFunnel"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesThe Sextant site ID.
funnelIdYes
objectIdNoOptional: a short link or tracking pixel of this site, to read its analytics instead of the site's.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered elsewhere. The description adds almost nothing beyond the fact that a single object (not a list) is returned; it says nothing about error behavior for a bad funnelId, the objectId override, or the shape of the returned funnel.

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?

A single short sentence with no filler and the key identifier provenance front-loaded. Its brevity borders on under-specification, but nothing in it is wasted or padded.

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

Completeness2/5

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

There is no output schema, so the description must carry the burden of explaining that a funnel definition (steps, configuration, metadata) is returned — and it does not. For a two-required-parameter read tool with no return documentation and no error context, the definition leaves clear gaps.

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 67% and funnelId carries no inline description; the description compensates by telling the agent where funnelId comes from, which is genuine added meaning. The remaining 33% gap (objectId is documented in the schema itself, so coverage of what's missing is minor) keeps this from being higher.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the resource ('one saved funnel') and implicitly the verb via the tool name, which is reasonably specific among the many 'getWebsite*' siblings. However, 'One saved funnel' does not distinguish fetching a funnel definition from fetching funnel stats, which is the distinction that actually matters next to analytics_getWebsiteFunnelStats and analytics_getWebsiteSavedFunnelStats. Purpose is only narrowly clearer than the name itself.

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?

The parenthetical 'funnelId from getWebsiteFunnels' gives useful provenance, implying the list tool must be called first to obtain an ID. There is no explicit when-to-use versus the *Stats or *Saved* variants, and no statement of what happens when the funnel is missing or belongs to another site.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources