@lodd/mcp-server

get_funnel

Compute conversion funnel by defining ordered steps of pageviews or custom events. Get per-step session counts and conversion rate relative to first step within same session.

Instructions

Compute a conversion funnel across an ordered sequence of pageview URLs and custom events. Returns per-step session counts and conversion rate relative to step 0. Steps must all occur within the same session, in order. Optional filters constrain which sessions enter the funnel.

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": {
      "site": "<site>",
      "steps": "<steps>"
    },
    "name": "get_funnel"
  }
}

Input Schema

Name	Required	Description	Default
`site`	Yes	Site domain or UUID
`steps`	Yes	Ordered steps — at least 1, typically 2-5
`period`	No	Time period	30d
`filter_os`	No	OS substring match (e.g. 'iOS')
`filter_browser`	No	Browser substring match (e.g. 'Chrome')
`filter_country`	No	2-letter country code (e.g. 'US')
`filter_utm_source`	No	Exact UTM source (e.g. 'twitter')
`filter_device_type`	No	Device type: 'desktop' \| 'mobile' \| 'tablet'
`filter_referrer_contains`	No	Referrer substring (e.g. 'google')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.15Jul 28, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It reveals important constraints (same session, in order) and the computation nature (per-step counts, conversion rate), but does not explicitly state that the tool is read-only or non-destructive. It adequately describes the behavioral aspects for a typical analytics tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences long, front-loaded with the primary purpose, and every word adds value. No redundancy or unnecessary detail.

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

Completeness4/5

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

Given the tool has 9 parameters and no output schema, the description covers the core functionality, output (per-step counts and conversion rate), and key constraints. It could mention return format or pagination, but for the complexity level, it is sufficiently complete.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds value beyond the schema by explaining the session constraint and that filters constrain which sessions enter the funnel. This provides context that is not evident from parameter descriptions alone.

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

Purpose5/5

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

The description uses specific verbs ('Compute a conversion funnel') and clearly defines the resource ('pageview URLs and custom events'). It explains the output ('per-step session counts and conversion rate relative to step 0') and distinguishes from sibling tools like get_event_sequences by focusing on funnel conversion with session constraints.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states when to use the tool ('Compute a conversion funnel across an ordered sequence') and provides constraints ('Steps must all occur within the same session, in order'). It mentions optional filters but lacks explicit guidance on when not to use or alternatives, though the context is clear.

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