TaskBullet

List delegated tasks

list_tasks

Read-onlyIdempotent

Retrieve recently delegated tasks for your account, including status, results, and confirmation flags, with optional status filtering.

Instructions

List recently delegated tasks for this account (id, title, status, short result). awaitingCustomerConfirm true means the delivery is done and the human must confirm, cancel, or reopen. amNote is the delivery note and deliverableLinks are https links from that note. pending and in_progress omit customer-cancelled jobs. cancelled is terminal.

Input Schema

Name	Required	Description	Default
`status`	No		all

Output Schema

Name	Required	Description	Default
`tasks`	No	Up to 50 recent tasks.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.2.0Oct 22, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / status / enum

Previous value: -[
-  "pending",
-  "in_progress",
-  "completed",
-  "failed",
-  "all"
-]New value: +[
+  "pending",
+  "in_progress",
+  "completed",
+  "failed",
+  "cancelled",
+  "all"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "tasks": {
+      "description": "Up to 50 recent tasks.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "amNote": {
+            "type": "string"
+          },
+          "awaitingCustomerConfirm": {
+            "description": "True means the human must confirm, cancel, or reopen.",
+            "type": "boolean"
+          },
+          "completedAt": {
+            "type": "string"
+          },
+          "createdAt": {
+            "type": "string"
+          },
+          "deliverableLinks": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "priority": {
+            "type": "string"
+          },
+          "result": {
+            "description": "Short result snippet when completed.",
+            "type": "string"
+          },
+          "status": {
+            "description": "pending, in_progress, completed, failed, or cancelled.",
+            "type": "string"
+          },
+          "taskId": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.1Oct 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description correctly spends its words elsewhere: it explains the awaitingCustomerConfirm gate (delivery done, human must confirm/cancel/reopen) and the terminal nature of 'cancelled'. It does not mention any bound on 'recently' (result cap or pagination), which is the one behavioral trait still missing.

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?

Four short sentences with the operation and returned fields front-loaded, followed by the interpretive notes an agent needs to read the flags correctly. No filler, though the field-by-field gloss overlaps with the output schema and could be tightened.

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?

With an output schema present and annotations covering the safety profile, the description only needs to add interpretation the structured data cannot: what awaitingCustomerConfirm means, how status buckets exclude cancelled jobs, and that 'cancelled' is terminal. For a one-parameter list tool this is sufficient, with pagination bounds the only minor omission.

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 description coverage is 0% across the single status parameter, so the description carries the burden and partially meets it by defining the semantics of 'pending', 'in_progress' (both omit customer-cancelled jobs) and 'cancelled' (terminal). 'completed', 'failed', and the 'all' default remain unaddressed, so the enum is not fully covered.

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 opens with a specific verb and resource ('List recently delegated tasks for this account') plus the shape of each returned row, which cleanly separates it from single-task siblings like get_task or confirm_task. An agent can identify both the operation and the scope without consulting 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 Guidelines3/5

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

Usage is implied by 'recently delegated tasks for this account', but the description never states when to prefer this over get_task or the mutation siblings (confirm_task, cancel_task, reopen_task), nor does it mention any prerequisite. Adequate for a simple listing tool, but no explicit routing guidance.

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

Deploy Server