Skip to main content
Glama

site_sessions

Read-only

List recorded browser sessions for a site, or read a single session's timeline step by step to inspect what happened during a shared browsing run.

Instructions

List recorded sessions for a site, or read one session's timeline step by step.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>"
    },
    "name": "site_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNo
siteYes
limitNoDefault 200 events.
sessionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. Beyond that the description adds the mode-switching behavior and the notion of reading a timeline incrementally, but says nothing about pagination, cursoring, ordering, or what a session/timeline record looks like.

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?

A single front-loaded sentence with the primary behavior first and the alternate mode second; nothing is padded. Minor loss for the vague 'step by step' phrasing, which adds words without adding precision.

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?

With four parameters, 25% schema coverage, and no output schema, the description should explain the unexplained 'from' parameter and the pagination/filtering model. It covers the high-level purpose and mode switch but leaves an agent unable to call the tool confidently when 'from' matters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%, with just 'limit' annotated (and confusingly as 'Default 200 events' for a session-listing tool), so the description carries the compensating burden. It clarifies that 'session' selects the single-session timeline mode, but leaves 'from' entirely unexplained and does not reconcile 'limit' being about events rather than sessions.

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 uses a specific verb+resource ('List recorded sessions for a site') and names a distinct second mode ('read one session's timeline step by step'), so an agent can tell the two behaviors apart. It stops short of 5 because 'timeline step by step' is suggestive rather than concrete about what a session record actually contains.

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?

The two modes are implied by which parameters are supplied, giving an agent a workable mental model. However, there is no explicit statement of when to use this over siblings, nor any stated prerequisites (e.g., that a valid 'session' identifier must first come from somewhere).

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