Skip to main content
Glama

list_tabs

Read-only

Lists the browser tabs available to the agent, including tabs the user shared and pages opened during the session. Use it to see which tabs can be read, clicked, or filled.

Instructions

List the browser tabs you can use. Normally these are the tabs the user shared by clicking Tether, plus tabs you or those pages opened. If the user has turned on bypass mode, every tab is listed.

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 observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, so the description's added value is scope semantics: which tabs appear in the normal case versus bypass mode. That is genuinely useful for interpreting results. It does not state ordering, whether closed/private tabs are excluded, or the shape of returned tab entries.

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?

Three short sentences, front-loaded with the purpose and followed by the scope caveats. Every sentence carries information; only the phrasing 'List the browser tabs you can use' is slightly loose versus the more precise explanation that follows.

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 zero-parameter read tool with no output schema, the description covers what set of tabs will be returned, which is the main ambiguity. It stops short of describing the return shape (e.g., tab identifiers needed for later click/close_tab calls), which would help an agent chain calls.

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 tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. No parameter semantics gap exists.

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 ('List') and resource ('browser tabs') and defines the scope precisely: tabs the user shared via Tether, tabs the agent or pages opened, and all tabs under bypass mode. This distinguishes it from the many other list_* siblings by resource, though it does not explicitly name any alternative.

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 implied by 'tabs you can use' — an agent can infer this is the discovery step before navigating, clicking, or closing a tab. However, there is no explicit when-to-use/when-not guidance and no pointer to sibling tools such as open_tab or request_bypass.

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