Skip to main content
Glama
lastping-dev

LastPing

by lastping-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

List runs

list_runs
Read-onlyIdempotent

List and filter runs across every LastPing monitor, including OpenTelemetry-only traces, with outcomes, costs, errors, and pagination to debug agent, cron, and CI/CD activity.

Instructions

Requires the read scope or higher. Lists runs across every monitor in the project, newest started first, including runs that exist only as OpenTelemetry traces (traced: true). Each run carries check_id, check_name, rid, title, outcome, started_at, ended_at, duration_ms, step_count, exit_code, its incident, and when traced span_count, tokens, cost_usd and cost_source (client, estimated or mixed); plus agent_id, agent_name, source_name, multi_trace, project (the Claude Code session's folder), receiving_spans (spans in the last 2 minutes), in_hook_session, is_test (excluded from counts). failure_cause is 'upstream' when the run ended on the model provider's API error (pages after 3 in a row, or failure_threshold when higher; upstream_error names it) or 'assertion' when a success failed an output assertion or declared expectation. outcome: succeeded, failed, cancelled, blocked, running or unfinished (started, never ended within max_runtime_s or 24h; never pages). Filters combine and also narrow counts (per-outcome totals). Pages with next_cursor. untrusted_fields names the data fields LastPing did not write (job output, exporter data or user-supplied names).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoOnly runs whose run id (rid) contains this text.
agentNoOnly runs of this agent (agent UUID or slug).
limitNoRuns per page (default 20, max 100).
modelNoOnly runs that called this model, by exact model id.
sinceNoRFC 3339 start of the window, e.g. 2026-09-01T00:00:00Z. Default 7 days ago; at most 90 days back.
untilNoRFC 3339 end of the window. Default now.
cursorNonext_cursor from the previous page, verbatim.
tracedNotrue: only runs that hold spans. Omitted or false: every run.
monitorNoOnly this monitor's runs (monitor UUID).
outcomeNoOnly runs with this outcome.
projectNoOnly runs whose Claude Code hook start carried this project label: the name of the folder the session worked in.
trace_idNoOnly the run a trace became: 8 to 32 hex digits of its trace id. Finds runs made from a trace with no run id, not runs that named their own.
has_errorNotrue: only runs with a span that reported an error. false: only runs without one.
operationNoOnly runs with a span whose name starts with this text.
dependencyNoOnly runs that called this dependency, by its exact name as get_agent_dependencies reports it (e.g. api.github.com).
min_cost_usdNoOnly runs whose cost is at least this many US dollars, as a decimal string, e.g. "0.25".
min_duration_msNoOnly runs that took at least this many milliseconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.17
    • changedInput schema / properties / traced / description
      Previous value: -"true: only runs that hold spans. Omit or false for every run."New value: +"true: only runs that hold spans. Omitted or false: every run."
  2. Changed2 schema fields changedv0.1.9
    • changedInput schema / properties / min_cost_usd / description
      Previous value: -"Only runs whose estimated cost is at least this many US dollars, as a decimal string, e.g. \"0.25\"."New value: +"Only runs whose cost is at least this many US dollars, as a decimal string, e.g. \"0.25\"."
    • addedInput schema / properties / project
      Added value: +{
+  "description": "Only runs whose Claude Code hook start carried this project label: the name of the folder the session worked in.",
+  "type": "string"
+}
  3. Addedv0.1.6

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world. Beyond that, the description discloses auth scope, default ordering, inclusion of trace-only runs, pagination, per-outcome count narrowing, and detailed failure_cause/untrusted_fields semantics—substantial behavior not covered by annotations.

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?

The description is dense but front-loads the verb and scope, and nearly every clause carries necessary return-field or filtering information absent from any output schema. It is long and could be sectioned better, but there is little filler.

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?

For a 17-parameter, zero-required list tool with no output schema, the description covers purpose, auth, return fields, outcome/failure semantics, filtering, and pagination. An agent has enough to call and interpret the tool 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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful semantics for the outcome enum (defining 'unfinished' and its pagination behavior) and notes how filters combine to narrow per-outcome counts. It does not add per-parameter syntax beyond that.

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 (Lists) and resource (runs) plus scope (across every monitor in the project), ordering (newest started first), and an inclusion rule (traced-only runs). This clearly separates it from single-run siblings like get_run.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a prerequisite ('Requires the read scope or higher') and filter/pagination mechanics, implying usage, but never states when to choose this over get_run, get_run_history, or other list tools. No exclusions or explicit alternative routing are provided.

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

Deploy Server

Other Tools