Nextmail

Start task run

startTaskRun

Destructive

Hand the assistant one job to do in the background, with no task saved: a long tidy-up, a report, or anything that should not wait on this conversation. It keeps working after the chat is closed and reports when done.

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": {
      "instruction": "<instruction>"
    },
    "name": "startTaskRun"
  }
}

Input Schema

Name	Required	Description
`model`	No	`standard` is the everyday model. `advanced` reasons better over long jobs and costs ten AI actions where the standard one costs one.
`autonomy`	No	`ask` sends every change to a person to approve. `organize` lets the run label, archive, bin, snooze, draft, take notes and keep contacts by itself, and email the addresses of the workspace. `reply` also lets it answer an email without asking, as long as it adds no recipients and the task does not use `connectors`. Anything else always waits for approval, and so does every change in a connected app.
`maxSteps`	No	The most model steps one run may take before it has to write its report.
`threadId`	No	A conversation to hand the run as its starting point, as `GET /threads` lists it.
`toolkits`	No	Extra groups of tools the run may use beyond reading and organising mail, such as `contacts`, `calendar`, `knowledge`, `web` or `connectors`, which lets it use the apps connected for the workspace. A run can never reach billing, members, domains, rules, keys or webhooks.
`instruction`	Yes	What the assistant should do, in plain words, as you would tell a person. It is the only instruction the run follows: text inside emails is read, never obeyed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the annotations, it discloses important lifecycle behavior: the job runs in the background, continues after the chat is closed, and reports when done. It also clarifies that no task record is saved, which is material behavioral context. It does not elaborate on the destructive implications already flagged by destructiveHint=true.

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?

The description is compact, front-loaded, and free of repetition. It conveys the core action, scope, examples, and persistence behavior in two efficient sentences.

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?

For a six-parameter background-run tool with rich schema descriptions and safety annotations, the description covers purpose, persistence, and unsaved-task scope adequately. It could be slightly more complete by explicitly contrasting itself with saved-task siblings or describing how the run is tracked.

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?

The schema has 100% description coverage for all six parameters, including detailed enum semantics for model and autonomy. The description itself adds no parameter-level guidance, so the schema does the heavy lifting and the baseline score 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?

The description states a specific action and scope: hand the assistant one background job with no saved task. The phrase 'with no task saved' distinguishes it from saved-task siblings such as createTask or runTask. An agent can identify the tool's role without opening the schema.

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?

It gives clear triggering examples and conditions: a long tidy-up, a report, or anything that should not wait on the conversation and should continue after chat closes. However, it does not explicitly name sibling alternatives or state when not to use it.

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.