Skip to main content
Glama
frsorrentino

Chrome Bridge

by frsorrentino
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_tabs

Read-onlyIdempotent

List all open browser tabs with their ID, URL, title, and active status. Optionally include window details for tab management.

Instructions

List every open tab with id, url, title, active flag and mine (created by this session). Read-only. Find a tab_id when the implicit target is not the one you mean. include_windows adds position, size, state and type of each window — needed before moving or tiling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_windowsNoAlso return the windows with bounds, state, type and tab count

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.15.0
    • addedInput schema / properties / include_windows
      Added value: +{
+  "default": false,
+  "description": "Also return the windows with bounds, state, type and tab count",
+  "type": "boolean"
+}
  2. First observedv1.8.0

TDQS

A4.4/5.0
Behavior4/5

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

The description states 'Read-only' and explains the 'mine' filter (tabs created by this session), which adds behavioral nuance beyond the annotations. It does not mention side effects, but the read-only nature is unambiguous and reinforced by annotations.

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 a single, efficient sentence that packs all essential information—purpose, fields, read-only nature, and parameter rationale—without any redundant wording.

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?

Given there is no output schema, the description adequately enumerates the returned fields for both tabs and windows. It also explains the 'mine' filter and the parameter's purpose. Minor omissions like sorting or pagination are not critical for this simple listing tool.

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?

The single parameter include_windows is explained in the description: it adds window details (position, size, state, type) and is needed before moving or tiling. This adds practical context beyond the schema's dry listing of fields.

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 tool lists all open tabs with specific fields (id, url, title, active, mine) and optionally windows. It also explains a key use case—finding a tab_id when the implicit target is ambiguous—which distinguishes it from similar tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly notes the tool is read-only and guides when to use it (to find a tab_id for other operations). While it doesn't name sibling tools like tab_action or create_tab, the context is clear enough for an agent to select this tool for listing tabs.

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