Skip to main content
Glama
t3ratech

T3rnel Browser — Session Bridge

Official
by t3ratech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

session_record_events

Read-onlyIdempotent

Fetch a recording's captured events in order, with pagination for long sessions. Returns browser events (click, scroll, keypress, input, navigation, focus, select, resize) for analysis or replay.

Instructions

Fetch the captured events of a recording, in the order they happened. Returns {events, count}, where count is the total held for the session and events is one page of {type, timestamp, tabId, data}; type is one of click, scroll, keypress, input, navigation, focus, select or resize. Page through long recordings with limit and offset rather than reading them whole, since a session can hold tens of thousands of events. Requires the T3rnel Browser extension.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum events to return in this page (default 100)
offsetNoNumber of events to skip, for paging through a long recording (default 0)
sessionIdYesRecording session to read, from session_record_list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.2.0
    • addedInput schema / properties / limit / default
      Added value: +100
    • addedInput schema / properties / limit / description
      Added value: +"Maximum events to return in this page (default 100)"
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / offset / default
      Added value: +0
    • addedInput schema / properties / offset / description
      Added value: +"Number of events to skip, for paging through a long recording (default 0)"
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • addedInput schema / properties / sessionId / description
      Added value: +"Recording session to read, from session_record_list"
  2. First observedv1.1.1

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses the paginated nature of the response, the return shape ({events, count}), the event type enum, and the requirement for the extension. This enriches the agent's understanding of actual behavior without contradicting annotations.

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 concise but information-dense, leading with the core purpose, then the return structure, paging advice, and the prerequisite. Every sentence adds value with no redundant phrasing, making it easy to scan and act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, paginated tool with simple parameters and no output schema, the description covers all needed aspects: return format, event types, paging behavior, and environmental requirement. An agent can correctly invoke this tool and process results without further clarification.

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?

All parameters are fully described in the schema (100% coverage), and the description adds practical context by explaining that limit and offset are for paging through recordings and that sessionId comes from session_record_list. This goes beyond the schema's basic definitions, providing meaningful usage insight.

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 clearly states the tool fetches captured events of a recording, specifying the order and the return structure. It distinguishes itself from sibling tools by focusing on reading events rather than recording or replaying them, making its purpose unambiguous.

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

Usage Guidelines4/5

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

Provides explicit guidance on paging through large sessions with limit and offset, and notes the prerequisite of the T3rnel Browser extension. It does not explicitly exclude alternatives like session_record_replay, but the context makes it clear this is for reading raw events, which is sufficient for most use cases.

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

Deploy Server

Other Tools