Skip to main content
Glama
lekt9

OpenReplay MCP Server

by lekt9

get_funnel_analysis

Analyze user funnels and conversion paths to understand user behavior patterns and identify drop-off points in user journeys.

Instructions

Analyze user funnels and conversion paths

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stepsYesFunnel steps in order
startDateNoStart date in ISO format
endDateNoEnd date in ISO format
filtersNoAdditional filters

Implementation Reference

  • The private async getFunnelAnalysis method that executes the tool logic for get_funnel_analysis. It currently returns a message stating that full implementation requires JWT authentication.
    private async getFunnelAnalysis(args: any) {
      // Funnel analysis requires JWT authentication
      return {
        content: [
          {
            type: "text",
            text: "Funnel analysis is not available via API key authentication. JWT authentication is required for this feature.",
          },
        ],
      };
  • Input schema defining the parameters for the get_funnel_analysis tool: steps (array of funnel steps), optional startDate, endDate, and filters.
    inputSchema: {
      type: "object",
      properties: {
        steps: {
          type: "array",
          description: "Funnel steps in order",
          items: {
            type: "object",
            properties: {
              name: { type: "string", description: "Step name" },
              eventType: { type: "string", description: "Event type (LOCATION, CLICK, CUSTOM)" },
              eventValue: { type: "string", description: "Event value to match" }
            }
          }
        },
        startDate: { type: "string", description: "Start date in ISO format" },
        endDate: { type: "string", description: "End date in ISO format" },
        filters: { type: "array", description: "Additional filters" }
      },
      required: ["steps"]
  • src/index.ts:200-224 (registration)
    Registration of the get_funnel_analysis tool in the list_tools handler, including name, description, and input schema.
    {
      name: "get_funnel_analysis",
      description: "Analyze user funnels and conversion paths",
      inputSchema: {
        type: "object",
        properties: {
          steps: {
            type: "array",
            description: "Funnel steps in order",
            items: {
              type: "object",
              properties: {
                name: { type: "string", description: "Step name" },
                eventType: { type: "string", description: "Event type (LOCATION, CLICK, CUSTOM)" },
                eventValue: { type: "string", description: "Event value to match" }
              }
            }
          },
          startDate: { type: "string", description: "Start date in ISO format" },
          endDate: { type: "string", description: "End date in ISO format" },
          filters: { type: "array", description: "Additional filters" }
        },
        required: ["steps"]
      }
    },
  • src/index.ts:290-291 (registration)
    Dispatch case in the CallToolRequest handler that routes calls to the getFunnelAnalysis method.
    case "get_funnel_analysis":
      return await this.getFunnelAnalysis(args);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Analyze' suggests a read operation, but the description doesn't specify whether this is a heavy computation, has rate limits, requires specific permissions, or what the output format looks like. For a tool with 4 parameters and no annotations, this is insufficient.

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 a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized and front-loaded with the essential information.

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?

Given the complexity of funnel analysis with 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the analysis returns, how results are structured, or any behavioral aspects like performance characteristics or prerequisites.

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%, so the schema already documents all parameters thoroughly. The description adds no additional meaning about parameters beyond what's in the schema. The baseline score of 3 is appropriate when the schema does the heavy lifting.

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 clearly states the tool's purpose as analyzing user funnels and conversion paths, which is a specific verb (analyze) and resource (user funnels/conversion paths). However, it doesn't distinguish this tool from sibling tools like get_user_journey or get_session_events, which might also analyze user paths.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like get_user_journey and get_session_events that might overlap in analyzing user paths, there's no indication of what makes this tool distinct or when it's the appropriate choice.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lekt9/openreplay-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server