Skip to main content
Glama
Sign In
pironjulien

nexus-browser

by pironjulien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_logs

Read-onlyIdempotent

Retrieves console errors and messages from a specified Chrome tab's DevTools, so you can inspect runtime issues and debug page behavior.

Instructions

Returns the stream of errors and messages from the tab's DevTools console.

Input Schema

NameRequiredDescriptionDefault
tab_idYesYour tab's id (from browser_new_tab, or a tab adopted with browser_adopt_tab).

Output Schema

NameRequiredDescriptionDefault
dataYes
statusYes
warningNoEmergency stop hotkey not held, or similar notice
untrusted_noteNoPage text that looks like instructions aimed at an AI

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv2.31.6
    • addedOutput schema / $defs
      Added value: +{
+  "LogEntry": {
+    "additionalProperties": true,
+    "properties": {
+      "method": {
+        "type": "string"
+      },
+      "params": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "timestamp": {
+        "type": "number"
+      }
+    },
+    "title": "LogEntry",
+    "type": "object"
+  }
+}
    • addedOutput schema / additionalProperties
      Added value: +true
    • addedOutput schema / description
      Added value: +"Console messages of the tab."
    • addedOutput schema / properties / data
      Added value: +{
+  "items": {
+    "$ref": "#/$defs/LogEntry"
+  },
+  "type": "array"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "title": "Result",
-  "type": "string"
-}
    • addedOutput schema / properties / status
      Added value: +{
+  "const": "success",
+  "type": "string"
+}
    • addedOutput schema / properties / untrusted_note
      Added value: +{
+  "description": "Page text that looks like instructions aimed at an AI",
+  "type": "string"
+}
    • addedOutput schema / properties / warning
      Added value: +{
+  "description": "Emergency stop hotkey not held, or similar notice",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "status",
+  "data"
+]
    • changedOutput schema / title
      Previous value: -"browser_logsOutput"New value: +"LogsAnswer"
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that output comes from the DevTools console, but 'stream' is ambiguous about whether this is a live stream, a snapshot, or how far back the logs go.

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?

It is a single, front-loaded sentence with no wasted words. It is efficiently structured, though the word 'stream' introduces ambiguity rather than clarity.

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?

With an output schema present and annotations covering safety and idempotency, the definition is nearly complete for a one-parameter read tool. The remaining gap is behavioral: it does not clarify snapshot versus live-stream semantics or log retention scope.

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 coverage is 100% for the single tab_id parameter, and the schema itself explains where tab IDs come from. The description adds no parameter semantics beyond what the schema already provides, so the baseline of 3 applies.

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?

It states a specific verb and resource: returns errors and messages from the tab's DevTools console. That distinguishes it from siblings like browser_content or browser_network_requests, though it does not explicitly name alternatives.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as browser_network_requests or browser_eval. The only signal is the implied debugging context of console logs.

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