Skip to main content
Glama
Sign In
chrome

chrome

by wellrccity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Manage tabs

tabs

Manage Chrome browser pages by listing, opening, focusing, closing, reloading, duplicating, pinning, or muting them by page ID.

Instructions

List, create, activate, close, reload, duplicate, pin or mute Chrome tabs. Actions: list, new, activate, close, get, reload, duplicate, pin, mute, unmute.

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

Input Schema

NameRequiredDescriptionDefault
urlNoURL for action="new". Defaults to about:blank.
tabIdNoTarget tab id. Defaults to the active tab.
actionNolist
activeNoFor action="new", whether to focus the new tab.
pinnedNo
timeoutNo
windowIdNo
waitUntilNo
bypassCacheNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state that 'close' is destructive, that 'reload'/'duplicate' mutate state, what permissions are needed, or how errors surface – for a multi-action mutation tool with zero annotation coverage this is a significant gap.

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?

Two short sentences that are front-loaded with the core verb list. The second sentence largely duplicates the schema's action enum, which is wasteful repetition, but the overall size is appropriate.

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?

With 9 parameters, 33% schema coverage, no annotations, and no output schema, the description is far too thin to call this tool correctly. It provides no return-value hints, no per-action parameter mapping, and no prerequisite or permission context.

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

Parameters2/5

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

Schema description coverage is only 33%, so five parameters (pinned, timeout, windowId, waitUntil, bypassCache) are undocumented everywhere, and the description compensates for none of them. It merely re-lists the action enum that the schema already defines, adding no meaning about url defaults, tabId fallback behavior, or waitUntil semantics.

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 concrete verbs and a clear resource (Chrome tabs), and enumerates the supported actions, so an agent knows it is the tab-management tool rather than a page-interaction sibling. However, the two sentences are internally inconsistent: the first omits 'get' and 'unmute' while the action list includes them, and no sibling is named for contrast.

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?

The description lists actions but never says when to use this tool versus navigate, snapshot, or click, nor when to prefer one action over another. Usage must be inferred entirely from the action names themselves.

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

Deploy Server

Other Tools