Skip to main content
Glama
nks-hub

rybbit-mcp

by nks-hub

User Journeys

rybbit_get_journeys
Read-onlyIdempotent

Analyze website user navigation paths to identify common page sequences and session flow patterns for optimization insights.

Instructions

Get user journey (flow) analysis showing the most common navigation paths through the site. Shows sequences of pages users visit and how many sessions follow each path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteIdYesSite ID (numeric ID or domain identifier)
startDateNoStart date (YYYY-MM-DD)
endDateNoEnd date (YYYY-MM-DD)
timeZoneNoIANA timezone (default UTC)
filtersNoFilters to apply
pastMinutesStartNoMinutes ago start
pastMinutesEndNoMinutes ago end
stepsNoNumber of journey steps to analyze (default 3)
journeyLimitNoMax number of journey paths to return (default 100)

Implementation Reference

  • The tool "rybbit_get_journeys" is registered here with its schema and handler function.
    server.registerTool(
      "rybbit_get_journeys",
      {
        title: "User Journeys",
        description:
          "Get user journey (flow) analysis showing the most common navigation paths through the site. Shows sequences of pages users visit and how many sessions follow each path.",
        annotations: {
          readOnlyHint: true,
          idempotentHint: true,
          openWorldHint: true,
          destructiveHint: false,
        },
        inputSchema: {
          siteId: siteIdSchema,
          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
            .number()
            .int()
            .min(2)
            .max(10)
            .optional()
            .describe("Number of journey steps to analyze (default 3)"),
          journeyLimit: z
            .number()
            .int()
            .optional()
            .describe("Max number of journey paths to return (default 100)"),
        },
      },
      async (args) => {
        try {
          const { siteId, steps, journeyLimit, ...rest } = args as {
            siteId: string;
            steps?: number;
            journeyLimit?: number;
            startDate?: string;
            endDate?: string;
            timeZone?: string;
            filters?: Array<{
              parameter: string;
              type: string;
              value: (string | number)[];
            }>;
            pastMinutesStart?: number;
            pastMinutesEnd?: number;
          };
    
          const params = client.buildAnalyticsParams(rest);
    
          if (steps !== undefined) params.steps = steps;
          if (journeyLimit !== undefined) params.limit = journeyLimit;
    
          const data = await client.get<JourneyPath[]>(
            `/sites/${siteId}/journeys`,
            params
          );
          return {
            content: [{ type: "text" as const, text: truncateResponse(data) }],
          };
        } catch (err) {
          const message = err instanceof Error ? err.message : String(err);
          return {
            content: [{ type: "text" as const, text: `Error: ${message}` }],
            isError: true,
          };
        }
      }
    );
  • The handler function for "rybbit_get_journeys" which processes the arguments and calls the Rybbit API.
    async (args) => {
      try {
        const { siteId, steps, journeyLimit, ...rest } = args as {
          siteId: string;
          steps?: number;
          journeyLimit?: number;
          startDate?: string;
          endDate?: string;
          timeZone?: string;
          filters?: Array<{
            parameter: string;
            type: string;
            value: (string | number)[];
          }>;
          pastMinutesStart?: number;
          pastMinutesEnd?: number;
        };
    
        const params = client.buildAnalyticsParams(rest);
    
        if (steps !== undefined) params.steps = steps;
        if (journeyLimit !== undefined) params.limit = journeyLimit;
    
        const data = await client.get<JourneyPath[]>(
          `/sites/${siteId}/journeys`,
          params
        );
        return {
          content: [{ type: "text" as const, text: truncateResponse(data) }],
        };
      } catch (err) {
        const message = err instanceof Error ? err.message : String(err);
        return {
          content: [{ type: "text" as const, text: `Error: ${message}` }],
          isError: true,
        };
      }
    }
Behavior3/5

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

Annotations declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds that results are ordered by 'most common' paths (indicating frequency sorting), but fails to disclose default values (steps=3, journeyLimit=100) or whether date ranges and pastMinutes are mutually exclusive.

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. The first sentence establishes the core operation (getting journey analysis), and the second clarifies the output format (sequences + session counts). Perfectly front-loaded.

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?

Given 9 parameters including complex nested filters and no output schema, the description is minimally adequate. It mentions the conceptual output (paths and counts) but omits structural details about the return format, aggregation methodology, or how the 'steps' parameter affects path depth analysis.

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?

With 100% schema description coverage including detailed filter dimension enumeration and default values in the schema, the baseline is 3. The description adds no parameter-specific guidance, but this is acceptable given the comprehensive schema documentation.

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 retrieves 'user journey (flow) analysis' showing 'navigation paths' and 'sequences of pages'. The parenthetical '(flow)' and specific mention of session counts effectively distinguishes this from sibling tools like rybbit_analyze_funnel, though it doesn't explicitly contrast with funnel analysis.

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 like rybbit_analyze_funnel, nor does it mention prerequisites (beyond the required siteId in schema) or the mutual exclusivity of date ranges versus pastMinutes parameters.

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