Skip to main content
Glama
Sign In
touch-browser

touch-browser

by nangman-infra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

List Session Tabs

tb_tab_list

Retrieve all daemon tabs registered for a given browser session to manage active tabs.

Instructions

List all daemon tabs registered for a session.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "tb_tab_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYesThe browser session to use for this operation.

Output Schema

NameRequiredDescriptionDefault
sessionIdYes
activeTabIdYes
tabsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.0
    • addedInput schema / properties / sessionId / description
      Added value: +"The browser session to use for this operation."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "activeTabId": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sessionId": {
+      "type": "string"
+    },
+    "tabs": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "active": {
+            "type": "boolean"
+          },
+          "currentUrl": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "hasState": {
+            "type": "boolean"
+          },
+          "latestSearchQuery": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "latestSearchResultCount": {
+            "minimum": 0,
+            "type": "integer"
+          },
+          "sessionFile": {
+            "type": "string"
+          },
+          "snapshotCount": {
+            "minimum": 0,
+            "type": "integer"
+          },
+          "tabId": {
+            "type": "string"
+          },
+          "visitedUrlCount": {
+            "minimum": 0,
+            "type": "integer"
+          }
+        },
+        "required": [
+          "tabId",
+          "active",
+          "sessionFile",
+          "hasState",
+          "visitedUrlCount",
+          "snapshotCount",
+          "latestSearchResultCount"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "sessionId",
+    "activeTabId",
+    "tabs"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.11

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only states it lists tabs but does not disclose side effects, prerequisites (e.g., session must exist), or whether the list is dynamic or static.

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?

The description is a single sentence, front-loaded and concise. However, it is so brief that it misses opportunities to add context.

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

Completeness3/5

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

Given the tool's simplicity and the presence of an output schema, the description is adequate but lacks details on return values or edge cases like an empty list.

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%, so the description adds little beyond the schema. The term 'daemon tabs' is slightly different from the title but still clear.

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 verb 'List' and the resource 'daemon tabs registered for a session', which is specific and distinct from sibling tools like tb_tab_open or tb_tab_close.

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?

No guidance on when to use this tool versus alternatives like tb_tab_select or tb_tab_open. The description implies listing but does not exclude other contexts.

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