OpenChrome

tabs_activate

Activate a specific Chrome tab to bring it into focus and confirm its document is visible. Switches the active tab visibly without relying on OS-level foregrounding.

Instructions

Explicitly activate an authorized Chrome tab and verify document visibility. Visibly changes the active tab; CDP-only mode never invokes an OS foreground helper.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tabId`	Yes	REQUIRED Target ID returned by tabs_create or tabs_context
`workerId`	No	Optional worker ownership scope to enforce before activation
`windowForeground`	No	Foreground path. Only cdp-only is supported; no OS process/window activation is attempted.	cdp-only

Output Schema

TableJSON Schema

Name	Required	Description	Default
`tabId`	Yes
`outcome`	Yes
`attempts`	Yes
`activated`	Yes
`pathTaken`	Yes
`superseded`	Yes
`activationSent`	Yes
`documentFocused`	Yes
`requestSequence`	Yes
`visibilityState`	Yes
`verificationError`	No
`windowForegroundAttempted`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.13.0Sep 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Explicitly discloses the visible active-tab change and states that no OS foreground helper is invoked in CDP-only mode; consistent with readOnly=false and destructive=false annotations, though it doesn't describe failure/authorization behavior.

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?

Two compact sentences convey purpose, side effect, and mode-specific behavior with no redundant wording.

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?

Covers the essential action, the visible side effect, and the CDP-only mode; since an output schema exists, omitting exact return fields is acceptable, but it does not mention potential error conditions.

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

Parameters5/5

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

Each parameter is enriched: tabId is defined as the target ID from tabs_create/tabs_context, workerId's ownership-check role is stated, and windowForeground's enum and side-effect-free nature are spelled out.

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?

Description uses a specific verb ('activate') and identifies the target ('authorized Chrome tab') plus a verification outcome, distinguishing it from tab creation, closing, or context retrieval.

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?

Indicates the primary use case and the CDP-only foreground behavior, but does not explicitly contrast with sibling tools such as tabs_create or tabs_context.

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

Deploy Server