Wiro MCP Server

Official

by wiroai

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

List Wiro tasks

list_tasks

Read-onlyIdempotent

List recent model tasks in your workspace or wiro.ai with status, cost, and initial outputs; use returned task IDs to retrieve full results.

Instructions

List recent model tasks in the API key's workspace (personal, or the key's team), newest first, from every project in it and from wiro.ai, with their status, cost and first outputs. Use it to find work from earlier conversations, then call get_task with a returned task ID for the complete result. Start times are Unix seconds. Steps of workflow runs and the runs Studio starts are not listed: list_workflow_runs and list_studio_results have those.

Input Schema

Name	Required	Description
`limit`	No	Maximum tasks to return (default 20, max 100).
`model`	No	A model or owner name, or part of one, e.g. "flux" or "flux-2-pro". Leave out the "owner/" part.
`start`	No	Pagination offset (default 0).

Output Schema

Name	Required	Description	Default
`limit`	Yes
`start`	Yes
`tasks`	Yes
`total`	Yes
`nextStart`	Yes
`nextAction`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.4.1Nov 1, 2026

changedInput schema / properties / model / description

Previous value: -"Optional model slug or partial model name filter."New value: +"A model or owner name, or part of one, e.g. \"flux\" or \"flux-2-pro\". Leave out the \"owner/\" part."

removedOutput schema / properties / tasks / items / properties / outputs / items / properties / url / format
```
Removed value: -"uri"
```

addedOutput schema / properties / tasks / items / properties / task / properties / chargedUsd

Added value: +{
+  "description": "What the payer was charged, after any discount.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / tasks / items / properties / task / properties / costUsd / description
```
Added value: +"The model's list price for this task."
```

Changed2 schema fields changedv1.3.0Aug 29, 2026

removedOutput schema / properties / tasks / items / properties / outputs / items / properties / text
```
Removed value: -{
-  "type": "string"
-}
```

addedOutput schema / properties / tasks / items / properties / outputs / items / properties / usage

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "input_tokens": {
+      "maximum": 1000000000000000,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "input_tokens_details": {
+      "additionalProperties": false,
+      "properties": {
+        "audio_tokens": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        },
+        "cache_write_1h_tokens": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        },
+        "cache_write_5m_tokens": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        },
+        "cache_write_tokens": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        },
+        "cached_tokens": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        },
+        "image_tokens": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        },
+        "text_tokens": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        },
+        "video_tokens": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        }
+      },
+      "type": "object"
+    },
+    "output_tokens": {
+      "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+    },
+    "output_tokens_details": {
+      "additionalProperties": false,
+      "properties": {
+        "accepted_prediction_tokens": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        },
+        "audio_tokens": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        },
+        "image_tokens": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        },
+        "reasoning_tokens": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        },
+        "rejected_prediction_tokens": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        },
+        "text_tokens": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        },
+        "video_tokens": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        }
+      },
+      "type": "object"
+    },
+    "server_tool_use": {
+      "additionalProperties": false,
+      "properties": {
+        "bash_code_execution_requests": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        },
+        "code_execution_requests": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        },
+        "computer_use_requests": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        },
+        "file_search_requests": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        },
+        "image_generation_requests": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        },
+        "text_editor_code_execution_requests": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        },
+        "web_fetch_requests": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        },
+        "web_search_requests": {
+          "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+        }
+      },
+      "type": "object"
+    },
+    "total_tokens": {
+      "$ref": "#/properties/tasks/items/properties/outputs/items/properties/usage/properties/input_tokens"
+    }
+  },
+  "required": [
+    "input_tokens",
+    "output_tokens",
+    "total_tokens"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedv1.2.3Aug 25, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Addedv1.2.1Aug 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive, open-world nature of the tool. The description adds useful behavioral context: API-key-scoped workspace visibility, newest-first ordering, returned status/cost/first outputs, Unix-second start times, and which task types are excluded. It stops short of explaining pagination behavior directly, though the schema covers that.

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 front-loaded with the primary list behavior and then adds only high-value details such as scope, ordering, next-step routing, and exclusions. Every sentence contributes useful information without redundancy.

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?

Given the rich schema coverage and the presence of an output schema, the description provides enough context for correct invocation. It covers what is listed, what is not listed, the workspace scope, and the recommended follow-up tool.

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 description coverage is 100%, so the parameters are already well documented. The description does not add meaningfully to the parameter semantics beyond noting Unix-second start times, which is more about returned data than the input parameters.

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 verb and resource ('List recent model tasks'), names the workspace scope, ordering, and included fields. It also explicitly distinguishes this tool from siblings by noting that workflow-run steps and Studio-run results are not listed here.

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

Usage Guidelines5/5

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

It gives a clear use case ('find work from earlier conversations') and a concrete next step ('call get_task with a returned task ID'). It also explicitly excludes two nearby task types and directs the agent to list_workflow_runs and list_studio_results instead.

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

Deploy Server