Skip to main content
Glama

tabs_batch

Perform multiple browser tab operations in one call: list, open, navigate, activate, resize, emulate, reload, go back/forward, or close tabs. Batch related tab actions to reduce round trips.

Instructions

Tab operations in one call: list, open/open_many, navigate, activate, resize, emulate, reload, back/forward, close.

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_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationsNoList of tab operations executed in order.
includeTabsNotrue always returns the tab list; false never does. Default: only when listed, tabs closed/opened in bulk, or unexpectedly changed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.6.1
    • addedInput schema / properties / includeTabs
      Added value: +{
      +  "description": "true always returns the tab list; false never does. Default: only when listed, tabs closed/opened in bulk, or unexpectedly changed.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / operations / items / properties / userAgent / oneOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / operations / items / properties / userAgent / type
      Removed value: -"string"
  2. First observedv0.4.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is largely covered. The description adds only the operation list; it says nothing about execution order, partial-failure behavior, or that 'close'/'close_browser' permanently discards tab state — a notable omission given destructiveHint=false.

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 that wastes no words and puts the batch scope first. The compressed slash notation ('open/open_many', 'back/forward') is slightly terse but readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-action batch tool with a large nested per-operation schema and no output schema, the description is thin: it does not explain action-to-field mapping, ordering guarantees, or error semantics. An agent can pick the tool but will likely need to inspect the schema closely to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Top-level schema coverage is 100% (operations, includeTabs both described), establishing the baseline of 3. However, the nested operation objects have almost no field-level descriptions and the description does not say which fields pair with which action (e.g., url vs urls vs waitUntil vs emulate fields).

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?

The description names the resource (tabs) and enumerates the concrete operations covered: list, open/open_many, navigate, activate, resize, emulate, reload, back/forward, close. That is specific enough to distinguish it from single-operation siblings, but it never explicitly contrasts itself with batch_actions or act_fast.

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

Usage Guidelines2/5

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

'In one call' hints that this is for bundling multiple tab actions, which is context, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer that a single tab action is handled here too versus in a sibling tool.

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