Skip to main content
Glama
Sign In
Browser[X]MCP

Browser[X]MCP

by rnd-pro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

batch_actions

Perform multiple browser actions in one batch—click, input text, scroll—to minimize API calls and speed up automation.

Instructions

Execute multiple actions in batch (up to 5 actions for performance)

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

Input Schema

NameRequiredDescriptionDefault
actionsYesArray of actions to execute in sequence

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-beta.1

TDQS

A3.6/5.0
Behavior2/5

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

The description discloses the 5-action limit and performance rationale, but it omits critical behavioral details such as execution order, error handling, atomicity, and whether actions share state. With no annotations to cover safety or side effects, the description leaves the agent without essential operational knowledge.

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?

The description is a single, front-loaded sentence that immediately conveys the main action and a useful constraint. It contains no extraneous words and is easy to parse.

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?

While the schema is detailed, the description fails to explain when batch execution is preferred over individual sibling tools, what the tool returns, or how it handles partial failures. No output schema exists, so the description should at least indicate the response format. The performance hint alone is insufficient for operational decision-making.

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?

The schema provides 100% coverage for the 'actions' parameter, including nested fields and descriptions. The tool description adds no parameter-specific meaning beyond restating the maxItems=5 constraint already present in the schema, so the baseline score of 3 applies.

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 clearly states the tool's purpose: 'Execute multiple actions in batch' with an explicit limit of 5 actions. This distinguishes it from sibling tools that handle single actions such as input_text or scroll_page.

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?

The phrase 'up to 5 actions for performance' provides clear context that batch execution is intended for efficiency when bundling multiple actions. It does not explicitly name alternatives or edge cases, but the performance rationale makes the use case evident.

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