Skip to main content
Glama
nks-hub

rybbit-mcp

by nks-hub

Funnel Step Sessions

rybbit_get_funnel_step_sessions
Read-onlyIdempotent

Retrieve user sessions that reached or dropped off at a specific funnel step to analyze drop-off causes and optimize conversion paths.

Instructions

Get the sessions that reached (or dropped off at) a specific funnel step. Useful for drilling into why users drop off at a particular funnel step.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteIdYesSite ID (numeric ID or domain identifier)
stepNumberYesThe funnel step number to get sessions for (1-indexed)
modeYes'reached' = sessions that made it to this step, 'dropped' = sessions that dropped off at this step
startDateNoStart date (YYYY-MM-DD)
endDateNoEnd date (YYYY-MM-DD)
timeZoneNoIANA timezone (default UTC)
filtersNoFilters to apply
pastMinutesStartNoMinutes ago start
pastMinutesEndNoMinutes ago end
stepsYesThe funnel steps definition (same as used in rybbit_analyze_funnel)
pageNoPage number, 1-indexed (default: 1)
limitNoResults per page (default: 20-50 depending on endpoint, max 200)

Implementation Reference

  • The handler for `rybbit_get_funnel_step_sessions` performs the API call to fetch funnel step sessions.
    async (args) => {
      try {
        const { siteId, stepNumber, mode, steps, ...rest } = args as {
          siteId: string;
          stepNumber: number;
          mode: "reached" | "dropped";
          steps: FunnelStep[];
          startDate?: string;
          endDate?: string;
          timeZone?: string;
          filters?: Array<{
            parameter: string;
            type: string;
            value: (string | number)[];
          }>;
          pastMinutesStart?: number;
          pastMinutesEnd?: number;
          page?: number;
          limit?: number;
        };
    
        const params = client.buildAnalyticsParams({ ...rest, page: rest.page ?? 1 });
        params.mode = mode;
    
        const data = await client.post(
          `/sites/${siteId}/funnels/${stepNumber}/sessions`,
          { steps },
          params
        );
        return {
          content: [{ type: "text" as const, text: truncateResponse(data) }],
        };
      } catch (err) {
        const message = err instanceof Error ? err.message : String(err);
        return {
  • Registration of the `rybbit_get_funnel_step_sessions` tool, including its schema definition.
    server.registerTool(
      "rybbit_get_funnel_step_sessions",
      {
        title: "Funnel Step Sessions",
        description:
          "Get the sessions that reached (or dropped off at) a specific funnel step. Useful for drilling into why users drop off at a particular funnel step.",
        annotations: {
          readOnlyHint: true,
          idempotentHint: true,
          openWorldHint: true,
          destructiveHint: false,
        },
        inputSchema: {
          siteId: siteIdSchema,
          stepNumber: z
            .number()
            .int()
            .min(1)
            .describe("The funnel step number to get sessions for (1-indexed)"),
          mode: z
            .enum(["reached", "dropped"])
            .describe("'reached' = sessions that made it to this step, 'dropped' = sessions that dropped off at this step"),
          startDate: z
            .string()
            .optional()
            .describe("Start date (YYYY-MM-DD)"),
          endDate: z
            .string()
            .optional()
            .describe("End date (YYYY-MM-DD)"),
          timeZone: z
            .string()
            .optional()
            .describe("IANA timezone (default UTC)"),
          filters: z
            .array(filterSchema)
            .optional()
            .describe("Filters to apply"),
          pastMinutesStart: z
            .number()
            .optional()
            .describe("Minutes ago start"),
          pastMinutesEnd: z
            .number()
            .optional()
            .describe("Minutes ago end"),
          steps: z
            .array(
              z.object({
                value: z.string().describe("Page path or event name"),
                type: z.enum(["page", "event"]).describe("Step type"),
                name: z
                  .string()
                  .optional()
                  .describe("Display name for the step"),
              })
            )
            .min(2)
            .describe("The funnel steps definition (same as used in rybbit_analyze_funnel)"),
          ...paginationSchema,
        },
      },
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, establishing safety profile. The description adds behavioral context by clarifying the 'reached' vs 'dropped' semantics (matching the mode enum), but does not disclose pagination behavior, rate limits, or response structure despite having no output schema.

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?

Two efficient sentences with zero waste. Front-loaded with the core function ('Get the sessions...') followed immediately by the value proposition ('Useful for drilling into...'). Every word earns its place.

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 12-parameter analytical tool with complex funnel definitions and no output schema, the description is minimal but adequate. The schema carries the parameter documentation weight, though the description could benefit from noting pagination or return value expectations.

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%, with all 12 parameters fully documented including complex filters and steps arrays. The description does not need to repeat parameter details, meeting the baseline score for high schema coverage.

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 verb 'Get' with clear resource 'sessions' and scope 'that reached (or dropped off at) a specific funnel step'. It effectively distinguishes from sibling rybbit_analyze_funnel by emphasizing individual session retrieval for drill-down analysis versus aggregate funnel metrics.

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?

Provides implied usage through 'useful for drilling into why users drop off', indicating the analytical context for using this tool. However, it lacks explicit when-not-to-use guidance or named alternatives (e.g., distinguishing from rybbit_analyze_funnel for aggregate views).

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/nks-hub/rybbit-mcp'

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