Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

list_tabs

List every open Google Chrome tab to inspect the current browser state and identify targets for navigation, switching, or automation.

Instructions

List all open tabs in Google Chrome

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_tabs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and "List" is the only signal that this is a safe read. It says nothing about what each entry contains (tab IDs, indices, titles, active state) or ordering, which is the critical behavior for a tool whose entire value is its output.

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?

A single front-loaded sentence with no filler, which is appropriate for a no-argument operation. It is arguably too terse rather than padded, so the brevity costs nothing structurally but leaves content gaps handled elsewhere.

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?

For a zero-parameter read tool the scope statement is close to sufficient, but with no output schema the description should indicate the shape of the returned tab list, since consumers need to know whether it yields handles usable by switch_to_tab. That single missing detail keeps it at minimum-viable rather than complete.

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 schema declares zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The absence of any filter arguments is also consistent with the "all open tabs" wording.

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?

States a specific verb and resource ("List all open tabs") plus the environment ("Google Chrome"), so the operation is unambiguous. It does not name or contrast with the closest siblings (get_current_tab, switch_to_tab), so sibling differentiation is left to inference.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the discovery step before switch_to_tab or close_tab. There is no explicit when-to-use, when-not-to-use, or named alternative anywhere in the text.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.