Turn Google Jules into a massively parallel AI coding workforce — batch-dispatch CLI + MCP server for Claude Code & Codex, with optional OpenAI-compatible task planning
Jules Dispatch has 7 tools with mixed quality. Naming is action-oriented (dispatch, batch, status, tail, wait, init, mcp) and mostly clear. However, descriptions vary significantly in depth. The dispatch and batch tools have reasonable descriptions (50-80 chars), but several tools lack sufficient context for LLM selection. Parameter schemas are present and mostly typed, but descriptions for many parameters are minimal or missing. No output schemas are documented. Error handling guidance is absent. The server is STDIO-only, which is a hard transport limitation.
Dispatch all .yaml/.yml/.json task files in a directory (supports multi-document YAML)
Dispatch a single task file to Jules. Use "-" to read from stdin.
Initialize a new Jules Dispatch project with .env template
Start the MCP server for Claude Code / Codex integration
Check status of recent Jules sessions
Stream activity from a Jules session until resolved or action is required
Monitor Jules sessions until resolved or action is required
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields without knowing response structure.
Parameter descriptions are minimal or absent. 'sessionId' in tail/wait lacks context; 'interval' and 'timeout' lack units/ranges; 'format' in dispatch lacks explanation of when to use yaml vs json.
No error handling guidance. Tools like dispatch and batch (WRITE operations) provide no recovery hints if a task fails or a file is malformed.
Tool 'mcp' has vague description ('Start the MCP server...') and unclear purpose. Parameter 'stdio' is undescribed. This tool's intent is ambiguous.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | 2026-07-28+ | v2 |
Numeric parameters lack bounds. 'parallel' (batch) has min/max (1-50), but 'scan' (status) lacks explicit range guidance; 'interval' and 'timeout' lack documented minimums/maximums in descriptions.