Skip to main content
Glama

batch_actions

Execute multiple macOS actions (clicks, typing, app launches) in one batch. Stops on first error. Returns a screenshot by default.

Instructions

PREFERRED: Always use this tool instead of calling individual action tools (click_at, type_text, press_key, launch_app, etc.) one at a time. Combine multiple steps into a single batch call — this is dramatically faster. Returns a single screenshot by default (disable with return_screenshot=false). Only use individual tools when you need to read the result of one action before deciding the next. Stops on first error. Max 20 actions per call.

Example — open Notes and write text (1 call instead of 6): [{ "action": "launch_app", "name": "Notes" }, { "action": "key", "key": "n", "modifiers": ["command"] }, { "action": "set_clipboard", "text": "Hello\nWorld" }, { "action": "key", "key": "v", "modifiers": ["command"] }]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionsYesArray of actions to execute sequentially
delay_between_msNoDelay between actions in ms (default 100)
return_screenshotNoReturn one screenshot at the end (default true). Set false for faster/smaller responses.
Behavior5/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 key behaviors: returns a single screenshot by default (configurable), stops on first error, max 20 actions, and mentions delay parameter. This is comprehensive for the tool's 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?

The description is highly concise: three sentences plus an example. It front-loads the key message (PREFERRED) and provides structured information about behavior and example usage. No wasted words.

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

Completeness5/5

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

Given the tool's complexity (many action types) and the absence of output schema, the description covers all needed aspects: purpose, usage guidelines, behavioral transparency, parameter semantics via example. It is complete enough for an agent to select and invoke correctly.

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 coverage is 100% with descriptions for each parameter. The description adds value by providing a concrete example showing how to structure the actions array, which aids understanding beyond schema definitions. However, the schema already enumerates all action types with properties, so the added semantic value is moderate.

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: to combine multiple steps into a single batch call, which is distinct from calling individual action tools. The verb 'combine' and the resource 'multiple steps' are specific and differentiate it from siblings.

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

Usage Guidelines5/5

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

Explicitly states 'PREFERRED: Always use this tool instead of calling individual action tools' and provides a clear when-not condition: 'Only use individual tools when you need to read the result of one action before deciding the next.' This gives excellent usage guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PeterHdd/macos-control-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server