Retrieve tab IDs from browser sessions, grouped by worker, with optional filtering by worker or summary counts.
Get session tab IDs grouped by worker.
| Name | Required | Description | Default |
|---|---|---|---|
| summary | No | Return counts only, no tab details | |
| workerId | No | Filter to a specific worker |
| Name | Required | Description | Default |
|---|---|---|---|
| workers | Yes | ||
| tabCount | Yes | ||
| sessionId | Yes | ||
| workerCount | Yes | ||
| defaultWorkerId | No |
Changes observed during successful MCP inspections.
v1.12.8Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description aligns but adds no further behavioral context (e.g., caching, performance implications). It does not contradict annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, well-structured sentence that immediately conveys the tool's function with no superfluous words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read tool with an output schema, the description is adequate. It covers the core functionality, though it could optionally mention the output format or grouping details.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for both parameters. The description adds no additional meaning beyond the schema's parameter descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Get session tab IDs grouped by worker.' clearly states the action (get), the resource (session tab IDs), and the grouping logic. It distinctively contrasts with sibling tools like tabs_close and tabs_create.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. No context about preferred scenarios, prerequisites, or exclusions is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.