Skip to main content
Glama

tabs_list

List open Zen tabs with the active tab first, including tab ID, title, and URL. Filter by title or URL to find tabs when many are open.

Instructions

List open tabs in Zen as "[tabId] title — url", with the tab the user is looking at first. Call this first. Shows up to limit other tabs; use query to search when there are many.

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": "tabs_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many other tabs to show, default 30
queryNoOnly tabs whose title or URL contains this text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does fairly well: it discloses the return format, the ordering guarantee (the tab the user is looking at comes first), and that `limit` applies to the other tabs rather than the total. It does not explicitly state the operation is read-only or non-mutating, which is the main remaining gap for a zero-annotation tool.

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?

Three short sentences, front-loaded with the core action and output shape, then ordering, then the call-order directive, then parameter hints. Nothing is padded or redundant.

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?

No output schema exists, so the description must describe return values — and it does via the format string and active-tab-first ordering. For a two-parameter read tool this is nearly sufficient; it could add one clause on whether tabs across multiple windows are included.

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?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by adding a usage heuristic for `query` (use it "when there are many" tabs) that the schema does not express. It also reinforces the "other tabs" semantics of `limit`, though that partly restates the schema text.

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?

States a specific verb and resource ("List open tabs in Zen") and even fixes the output shape as "[tabId] title — url", so the agent knows exactly what comes back. "Call this first" positions it relative to the sibling tab tools (tab_create, tab_close) without ambiguity.

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?

Gives explicit sequencing guidance ("Call this first") and a concrete condition for the search path ("use `query` to search when there are many"). It stops short of stating when-not to use it or what to do after listing, but the primary routing decision is covered.

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