Skip to main content
Glama

run

Destructive

Execute pending tasks from an existing devplan. Preview changes with dry_run or run a single task by task_id.

Instructions

Execute a project's ALREADY-PLANNED pending tasks (a devplan).

Use when: tasks already exist (from a prior ``plan`` or a devplan directory)
and you want to execute them. Do NOT use when: no plan exists and you are
starting from a goal — that is ``build``'s job (it analyzes and decomposes).
Related: ``build`` (plan + execute a goal), ``status`` (see the task ids).
Pass ``task_id`` to run a single task.

DESTRUCTIVE side effects: edits files and makes git commits, and calls an
external LLM provider (open-world, non-idempotent). ``dry_run=True`` previews
without changing anything.

Returns a short text summary of what was run or previewed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path to a registered project's directory that already has planned tasks (a devplan). Example: '/Users/me/code/my-api'.
dry_runNoWhen true, preview the tasks that would run without executing or editing anything. Example: true.
task_idNoRun only this single task id (as shown by ``status``); omit to run all pending tasks in dependency order. Example: '010-add-auth'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Adds detail beyond annotations: specifies destructive effects (edits files, git commits, external LLM calls) and non-idempotency. Mentions dry_run to preview.

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 concise paragraphs: purpose/usage, side effects, return value. Front-loaded with key info.

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?

Covers purpose, when to use/not, side effects, return format, and parameter guidance. No gaps given schema and annotations.

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 100% with clear param descriptions. Description adds context on task_id usage ('run a single task') but mostly redundant with schema. Slight value added.

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?

Clearly states verb 'Execute' on resource 'ALREADY-PLANNED pending tasks (a devplan)'. Differentiates from sibling tools like build and status.

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 says when to use (tasks already exist) and when not (no plan, starting from goal, use build instead). Names related tools.

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/dcondrey/misterdev'

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