Skip to main content
Glama
xav-ie

Browser Session MCP

by xav-ie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

list_visits

Read-only

Lists a browser session's page visits oldest first so you can choose the numbered visit to inspect that page load's console and network logs.

Instructions

List the session's page visits, oldest first. Each visit is one top-level navigation in one tab, numbered by seq; pass that number as visit to list_console_messages or list_network_requests to see only that page load's logs. Use it to find which page load to inspect; use list_pages for the tabs open now. It reads logs and changes nothing. Empty unless the listener role is running, and deleted when the session closes.

Input Schema

NameRequiredDescriptionDefault
sessionIdYesThe id returned by open_browser_session. Errors if no open session has it.

Output Schema

NameRequiredDescriptionDefault
visitsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.5
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "VisitHeader": {
+      "properties": {
+        "openedAt": {
+          "type": "string"
+        },
+        "seq": {
+          "format": "uint32",
+          "minimum": 0,
+          "type": "integer"
+        },
+        "targetId": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "seq",
+        "targetId",
+        "url",
+        "openedAt"
+      ],
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "properties": {
+    "visits": {
+      "items": {
+        "$ref": "#/$defs/VisitHeader"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "visits"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / sessionId / description
      Added value: +"The id returned by open_browser_session. Errors if no open session has it."
  3. First observedv0.1.2

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so 'reads logs and changes nothing' is largely redundant. The description does add real behavioral context the annotations can't: ordering (oldest first), the lifecycle rule that visits are deleted when the session closes, and the empty-unless-listener-running condition. Missing only details like result caps or retention limits.

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?

Four short sentences, front-loaded with what the tool lists and its ordering, then routing to related tools, safety, and preconditions. No filler.

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?

A read-only listing tool with one fully-described parameter and an output schema. Ordering, the seq/visit contract, empty-state precondition, and lifecycle are all covered; nothing an agent needs to invoke it is missing.

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?

With one param fully documented in the schema, the 3 baseline applies; the description goes beyond it by explaining what a visit's seq means and that the number is what should be passed as `visit` to other tools. It doesn't describe the sessionId parameter itself, but the schema already does.

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?

States the specific resource (session page visits) and scope (oldest first, one top-level navigation per tab, numbered by seq). Explicitly distinguishes itself from list_pages ('for the tabs open now') and names the downstream consumers list_console_messages and list_network_requests.

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?

Gives explicit use case ('find which page load to inspect') and the alternative to pick instead (list_pages for currently open tabs). Also states the precondition 'Empty unless the listener role is running', which tells the agent when the tool will yield nothing.

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