Skip to main content
Glama

run_group

Runs every test in a group in order, either on an existing session or on a new cloud device started and stopped automatically. Returns a run id to fetch results with get_run.

Instructions

Run every test of a group in order. With session_id it runs on that session; without it, on a new device of the app platform that VibeView starts and stops (it does not use a session you hold from dev_start; pass session_id to run on a session you hold). Returns a run id for get_run.

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": {
      "group": "<group>"
    },
    "name": "run_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupYesGroup id (from the Tests page or `vibeview list-suites`).
ai_useNosmart (default): replays recorded and learned paths, and uses AI only where the screen changed or a step has no path yet; no_ai: replays only, no AI and no usage credit (a step with no path is not checked); ai_only: the AI does every step.
session_idNoRun on this session instead of a new device.
device_modelNoDevice model for a new device; omitted: any free one. A model of another platform (same form factor) runs the group's app for that platform: the app linked in its app family, else the app with the same bundle id / package. The reply names the platform and app the run went to.
start_from_current_screenNoWith session_id: no reset before the first test.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, so the description carries most of the load and does real work: it discloses that VibeView provisions and tears down its own device, that existing dev_start sessions are ignored, and that a run id is returned for get_run. It stops short of covering cost, duration, or failure behavior when a test in the group fails.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and kept to three sentences with no filler. The nested parenthetical about dev_start is slightly awkward to parse but the information is genuinely useful, so it earns its place.

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

Completeness4/5

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

With no output schema, the description correctly notes that a run id is returned and points to get_run for results. For a five-parameter execution tool, the remaining gap is failure and timeout behavior, which an agent would benefit from but can discover via get_run.

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%, so the baseline is 3, and the description earns an extra point by explaining session_id's effect (a session you hold versus a freshly started device) and by clarifying that start_from_current_screen only applies with a session. The ai_use and device_model semantics are left to the already-thorough schema.

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?

States a specific verb and resource with scope: "Run every test of a group in order." The word "every" distinguishes it from the sibling run_test, and the description names dev_start explicitly in the session discussion, so an agent can tell which tool to reach for.

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?

Gives clear conditional guidance on the main branching decision: with session_id it runs on that session, without it a new device is started and stopped. It also rules out a plausible mistake by warning that a session held from dev_start is not reused unless passed. It does not state when to prefer run_group over run_test, but the "every test of a group" phrasing implies the boundary.

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