Skip to main content
Glama
yinnho

AginxBrowser

by yinnho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust

session_console

Read-only

Fetch a session's recent browser console output (log, info, warn, error) filtered by level, time, URL, or limit. Use it to identify why a page misbehaves by reading the exact error messages.

Instructions

Read the session's recent page console output (log/info/warn/error) as {url, total, matched, messages:[{ts_ms, level, text, url}]}, newest last. Ring buffer of 500 entries; captures output from page scripts, clicks, evals and navigation alike. Optional filters: level (exact, e.g. "error"), since_ts (epoch ms), url_contains (page URL substring), limit (most recent N matches). The fastest way to see WHY a page misbehaves: click the button, call this, read the error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelNoOnly entries at this level: "log" | "info" | "warn" | "error"
limitNoKeep only the most recent N matching entries
since_tsNoOnly entries logged at or after this Unix epoch millisecond timestamp
session_idYesSession ID
url_containsNoOnly entries whose page URL contains this substring

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.1
    • removedInput schema / title
      Removed value: -"SessionConsoleParams"
  2. Changed5 schema fields changedv0.3.0
    • addedInput schema / properties / level
      Added value: +{
+  "default": null,
+  "description": "Only entries at this level: \"log\" | \"info\" | \"warn\" | \"error\"",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "default": null,
+  "description": "Keep only the most recent N matching entries",
+  "format": "uint",
+  "minimum": 0,
+  "type": [
+    "integer",
+    "null"
+  ]
+}
    • addedInput schema / properties / since_ts
      Added value: +{
+  "default": null,
+  "description": "Only entries logged at or after this Unix epoch millisecond timestamp",
+  "format": "uint64",
+  "minimum": 0,
+  "type": [
+    "integer",
+    "null"
+  ]
+}
    • addedInput schema / properties / url_contains
      Added value: +{
+  "default": null,
+  "description": "Only entries whose page URL contains this substring",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedInput schema / title
      Previous value: -"SessionCookiesParams"New value: +"SessionConsoleParams"
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds meaningful behavioral context: it is a ring buffer of 500 entries, newest last, and captures output from multiple sources. This goes beyond the annotation and helps the agent understand the tool's memory and ordering behavior.

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 compact, front-loaded with the return shape, and every sentence adds value. The final sentence is a memorable usage heuristic, and there is no filler.

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?

For a read-only tool with a fully documented schema, the description covers the return shape, ordering, buffer size, capture scope, and filters. It doesn't explain pagination or what happens when the buffer overflows, but those are minor gaps given the tool's simplicity and the readOnlyHint annotation.

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?

Schema description coverage is 100%, so the schema already documents all five parameters. The description adds a little extra context by grouping filters and giving an example value for level, but it doesn't substantially extend the schema's meaning.

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 states a specific verb ('Read'), a clear resource ('the session's recent page console output'), and the exact return shape. It also distinguishes itself from siblings by focusing on console output, not network, state, or storage.

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?

The description explicitly says this is 'The fastest way to see WHY a page misbehaves' and gives a concrete workflow: 'click the button, call this, read the error.' It also clarifies that it captures output from page scripts, clicks, evals, and navigation, which helps an agent know when to use it over alternatives like session_network or session_state.

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