Skip to main content
Glama

batch_execute

Batch multiple MOHO operations into a single IPC call to reduce latency and improve efficiency. Group related reads, writes, or animation updates.

Instructions

Execute multiple MOHO operations in a single IPC round-trip (~300ms total) instead of one round-trip per call (~300ms each). PREFER THIS over individual calls whenever you have 2+ operations.

Method names use DOT notation: "bone.setTransform", "layer.getProperties", "animation.setKeyframe", etc. Params match each tool's schema exactly.

Supports all methods EXCEPT: document.screenshot (too slow), batch.execute (no nesting).

Common patterns:

  • Multi-frame animation: batch bone.setTransform across frames 1,5,10,15,...

  • Bulk reads: batch document.getInfo + document.getLayers + layer.getProperties for several layers

  • Keyframe + easing: batch animation.setKeyframe then animation.setInterpolation for each

  • Multi-bone pose: batch bone.setTransform for each bone in a skeleton at the same frame

  • Layer setup: batch layer.setName + layer.setVisibility + layer.setOpacity

Returns { results: [{ success, index, result|error }], summary: { total, executed, succeeded, failed, stoppedEarly } }. Use stopOnError: true when later operations depend on earlier ones succeeding.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationsYesArray of operations to execute sequentially
stopOnErrorNoIf true, stop executing after the first failed operation
Behavior5/5

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

With no annotations, the description fully carries behavioral disclosure. It explains performance characteristics, unsupported methods, sequential execution implied by stopOnError guidance, and the exact return structure including per-operation success/error results.

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 well-structured with a clear opening, bulleted patterns, and a closing return-format summary. Every sentence contributes essential information, and the content is organized for quick scanning.

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 (batching arbitrary operations) and lack of output schema, the description is complete: it covers input format, limitations, return structure, and error handling. The examples cover common use cases sufficiently for an agent to 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?

The schema already covers both parameters well (100% coverage). The description adds meaningful value by clarifying dot-notation format for method names, stating that params match each tool's schema exactly, and providing example usage patterns that aid parameter construction.

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 function: executing multiple MOHO operations in a single IPC round-trip. It distinguishes itself from sibling tools by explicitly mentioning 'PREFER THIS over individual calls' and listing supported method types.

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?

Provides explicit when-to-use guidance ('whenever you have 2+ operations'), exclusions (document.screenshot, batch.execute), and common usage patterns with concrete examples. Also advises using stopOnError when operations are dependent, which is actionable 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/neosh11/moho-mcp-server'

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