Skip to main content
Glama
Sign In
Chrome Browser Control

Chrome Browser Control

by vKongv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Perform sequential page actions

perform_actions

Execute up to ten browser actions—click, type, keypress, scroll—in one document target with a validated document ID, and stop on the first error. Use for reliable multi-step page automation.

Instructions

Run up to 10 sequential page actions in one document target. An explicit batch-level documentId is revalidated before every step and after observation; steps cannot override it. Fail-fast on the first step error. Click, type, and keypress steps fail with DOCUMENT_HIDDEN on hidden documents unless that step sets allowHidden=true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "actions": "<actions>"
    },
    "name": "perform_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoOptional act-then-observe requests, run after the page action in waitFor, snapshot, pageStatus order.
tabIdNoOptional Chrome tab id. Defaults to the claimed session tab, then the active tab.
actionsYesOrdered action steps. Each step is a flat object with action plus action-specific fields.
documentIdNoExact frame document id returned by list_frames. Omit to target the current top document.
sessionTabIdNoOptional claimed tab session id returned by claim_tab.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses fail-fast behavior, DOCUMENT_HIDDEN failure for click/type/keypress unless allowHidden=true, and documentId revalidation before every step and after observation. This is substantive behavioral context beyond the schema, though it does not cover scroll-specific behavior or return values.

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 sentences with zero redundancy. The main purpose is front-loaded, and each subsequent sentence adds a critical behavioral constraint. It is compact and well-structured.

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?

The description covers the core behavior (batch execution, fail-fast, hidden handling) but does not mention the 'after' observation feature or other parameters like tabId/sessionTabId. However, those are fully described in the schema, and the description provides enough high-level context for an agent to understand the tool's primary function and constraints.

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 description coverage is 100%, so baseline is 3. The description adds meaning beyond the schema by explaining documentId revalidation (steps cannot override it) and the allowHidden exception for hidden documents. These nuances are not present in the parameter descriptions themselves.

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?

The description states a specific verb and resource: 'Run up to 10 sequential page actions in one document target.' It clearly distinguishes this from sibling tools like click/type/scroll by emphasizing batch execution and the single-document constraint. The mention of fail-fast and DOCUMENT_HIDDEN behavior further clarifies its role.

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

Usage Guidelines3/5

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

The description implies this is for batching multiple actions, but it does not explicitly contrast with single-action siblings (click, type, scroll) or state when to prefer this tool over them. The documentId revalidation and hidden-document notes give some context, but no explicit 'use this for multiple actions; use click for a single action' guidance.

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