Skip to main content
Glama
nks-hub

rybbit-mcp

by nks-hub

Session Detail

rybbit_get_session
Read-onlyIdempotent

Retrieve comprehensive session analytics including page views, events, user traits, device information, location data, and complete event timeline for detailed user behavior analysis.

Instructions

Get detailed session information including all page views, events, user traits, device info, location, and full event timeline. Use rybbit_list_sessions first to find session IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteIdYesSite ID (numeric ID or domain identifier)
sessionIdYesSession ID to retrieve

Implementation Reference

  • Registration and handler implementation for the 'rybbit_get_session' tool.
    server.registerTool(
      "rybbit_get_session",
      {
        title: "Session Detail",
        description:
          "Get detailed session information including all page views, events, user traits, device info, location, and full event timeline. Use rybbit_list_sessions first to find session IDs.",
        annotations: {
          readOnlyHint: true,
          idempotentHint: true,
          openWorldHint: true,
          destructiveHint: false,
        },
        inputSchema: {
          siteId: siteIdSchema,
          sessionId: z.string().describe("Session ID to retrieve"),
        },
      },
      async (args) => {
        try {
          const { siteId, sessionId } = args as {
            siteId: string;
            sessionId: string;
          };
    
          const data = await client.get<SessionDetail>(
            `/sites/${siteId}/sessions/${sessionId}`
          );
    
          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,
          };
        }
      }
    );
Behavior4/5

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

Annotations declare read-only, idempotent, non-destructive safety. The description adds valuable context about data richness ('full event timeline') and scope that annotations don't cover. Minor gap: doesn't mention behavior when sessionId is not found (though openWorldHint=true suggests graceful handling).

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 sentences, zero waste. First sentence establishes capability and return payload; second establishes prerequisite workflow. Front-loaded with the action verb and comprehensive data description. No redundant phrases.

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 2 simple parameters with full schema coverage and good annotations, description adequately compensates for missing output schema by detailing return content (page views, events, timeline). Minor gap: could note if 'full event timeline' implies pagination or large payloads.

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 has 100% coverage with clear descriptions. The description adds workflow context for sessionId ('Use rybbit_list_sessions first to find session IDs'), explaining provenance beyond the schema's 'Session ID to retrieve'. Exceeds baseline 3 by connecting parameters to sibling tool usage.

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?

Description uses specific verbs ('Get detailed session information') and enumerates exact data categories returned (page views, events, user traits, device info, location, full event timeline). The mention of 'session IDs' distinguishes this from the sibling list_sessions tool.

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

Usage Guidelines5/5

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

Explicitly states the prerequisite workflow: 'Use rybbit_list_sessions first to find session IDs.' This clearly establishes when to use the sibling discovery tool versus this detail retrieval tool, preventing agent errors from calling get_session without valid IDs.

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