Skip to main content
Glama

List phone runs

list-phone-runs-tool
Read-only

List the runs queued on one phone (device commands, macros and GUI-agent tasks) that the authenticated user can see, newest first, with their status, result and error. Use get-phone-run-tool to poll a single 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": {
      "slot": "<slot>"
    },
    "name": "list-phone-runs-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, defaulting to 1.
slotYesPhone slot UUID from list-phones-tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slot / description
      Previous value: -"Phone slot UUID from list-phones."New value: +"Phone slot UUID from list-phones-tool."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine context beyond that: newest-first ordering, visibility scoping to the authenticated user, and the fact that each run carries status, result and error. It stops short of describing pagination behavior or result-set size, which would be the remaining behavioral detail.

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?

Two sentences with no filler. The scope-and-ordering statement is front-loaded, and the second sentence is purely a routing pointer to the sibling, so every clause 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 takes on the burden of indicating return content and does so by naming status, result and error plus newest-first ordering and user-scoped visibility. The one gap is that pagination semantics (whether `page` signals more results, any total count) are left unstated, which matters for a list tool that can grow unbounded.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema itself documents both `slot` (as a UUID from list-phones-tool) and `page` (default 1). The description reinforces that only one phone is targeted but adds no format or defaulting detail the schema does not already state, so the baseline of 3 applies.

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 (list) and resource (runs queued on one phone), enumerates the run types covered (device commands, macros, GUI-agent tasks), and specifies ordering (newest first). It is immediately distinguishable from get-phone-run-tool, which the description explicitly frames as the single-run counterpart.

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?

Names the alternative that matters most here — 'Use get-phone-run-tool to poll a single run' — and the condition that selects it, which is exactly the confusion risk with a list/get pair. It does not cover other adjacency questions (e.g., when to use list-automation-runs-tool instead), but it gives clear context for the primary routing decision.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources