Skip to main content
Glama
lekt9

OpenReplay MCP Server

by lekt9

get_session_details

Retrieve comprehensive session data including events, errors, network requests, console logs, and performance metrics to analyze user behavior patterns.

Instructions

Get detailed information about a specific session including all events, errors, network requests, console logs, custom events, and performance metrics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesThe session ID to retrieve

Implementation Reference

  • The handler function implementing the logic for the get_session_details tool. It notes that full details are unavailable with API key auth and recommends alternatives.
    private async getSessionDetails(args: any) {
      const { sessionId } = args;
      // Session replay details not available via v1 API
      // Only events are available
      return {
        content: [
          {
            type: "text",
            text: "Session replay details are not available via API key authentication. Use get_session_events instead or use JWT authentication for full access.",
          },
        ],
      };
    }
  • Input schema for the get_session_details tool, defining a required 'sessionId' string parameter.
    inputSchema: {
      type: "object",
      properties: {
        sessionId: { type: "string", description: "The session ID to retrieve" }
      },
      required: ["sessionId"]
    }
  • src/index.ts:110-120 (registration)
    Registration of the get_session_details tool in the ListTools response, including name, description, and input schema.
    {
      name: "get_session_details",
      description: "Get detailed information about a specific session including all events, errors, network requests, console logs, custom events, and performance metrics",
      inputSchema: {
        type: "object",
        properties: {
          sessionId: { type: "string", description: "The session ID to retrieve" }
        },
        required: ["sessionId"]
      }
    },
  • src/index.ts:280-281 (registration)
    Dispatch case in the CallToolRequestHandler that routes calls to the getSessionDetails handler method.
    case "get_session_details":
      return await this.getSessionDetails(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. It describes what information is retrieved but lacks details on permissions needed, rate limits, pagination, error handling, or the format of returned data. For a tool that fetches comprehensive session details, this omission is significant.

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

Conciseness4/5

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

The description is a single, efficient sentence that front-loads the core action and lists included information without unnecessary words. It could be slightly improved by structuring the list more clearly, but it avoids redundancy and is appropriately sized for the tool's complexity.

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 tool's complexity (retrieving multiple data types) and lack of annotations or output schema, the description is incomplete. It doesn't explain the structure of returned data, potential limitations, or how to interpret the detailed information, leaving gaps for effective agent use.

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?

The input schema has 100% description coverage, with the single parameter 'sessionId' clearly documented. The description adds no additional semantic context about the parameter, such as format examples or validation rules, but the schema's completeness justifies the baseline score of 3.

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 with a specific verb ('Get') and resource ('detailed information about a specific session'), and it enumerates the types of information included (events, errors, network requests, etc.). However, it doesn't explicitly distinguish this tool from similar siblings like 'get_session_events' or 'get_performance_metrics', which reduces clarity about its unique scope.

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_session_events' and 'get_performance_metrics' available, it fails to specify scenarios where this comprehensive tool is preferred over more focused ones, or any prerequisites for its use.

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