Nextmail

List task runs

listTaskRuns

Read-only

List runs of assistant tasks, newest first, optionally for one task or one state. Each line gives the run id, its task, its state, what started it and how many steps it took.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listTaskRuns"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`cursor`	No
`status`	No	Only the ones in this state.
`taskId`	No	Only what belongs to this task.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A4/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 goes beyond by disclosing ordering ('newest first') and the exact fields returned per line (run id, task, state, trigger, step count), which is real added context. It omits pagination/cursor behavior, keeping it from a 5.

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 tight sentences with zero filler; ordering and scoping constraints are front-loaded before the field breakdown. Every clause carries information an agent needs.

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 usefully explains the shape of each returned line, which is a real gap-filler. What's missing is how cursor/limit interact for fetching further pages of what could be a long run list.

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 50%: status and taskId are described in the schema, while limit and cursor have none. The description's 'optionally for one task or one state' reinforces the two documented filters but adds no syntax or meaning for limit or cursor, leaving the undocumented half unaddressed.

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 ('List runs of assistant tasks') plus scope ('newest first, optionally for one task or one state'). It is clearly distinguishable from getTaskRun (single run detail) and listTasks (the tasks themselves).

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 optional filters ('for one task or one state') imply how to narrow the listing, but it never names an alternative such as getTaskRun for full run details or listTasks for the parent objects. Usage is inferable rather than stated.

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

All Nextmail tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.