zhenzhen-nanobanana-mcp

Get Image Tasks

get_image_tasks

Read-onlyIdempotent

Retrieve persisted image task statuses and absolute output paths without resubmitting upstream jobs. Filter by task IDs or paginate using a cursor.

Instructions

查询持久任务与图片绝对路径，不重新提交上游。可按task_ids筛选或用next_cursor分页。

queued/preparing/running正常返回；failed/unknown/cancelled返回isError并保留全部状态。 checkpointer是本地SQLite字符串命名空间，不是路径、LangGraph对象或认证凭据。

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": {
      "checkpointer": "<checkpointer>",
      "thread_id": "<thread_id>"
    },
    "name": "get_image_tasks"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No
`task_ids`	No
`thread_id`	Yes
`checkpointer`	Yes

Output Schema

Name	Required	Description	Default
`tasks`	Yes
`thread_id`	Yes
`next_cursor`	No
`checkpointer`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.3.1Oct 23, 2026

addedOutput schema / properties / tasks / items / properties / file_integrity

Added value: +{
+  "default": "not_checked",
+  "enum": [
+    "not_checked",
+    "verified",
+    "failed"
+  ],
+  "title": "File Integrity",
+  "type": "string"
+}

addedOutput schema / properties / tasks / items / properties / post_attempts

Added value: +{
+  "default": 0,
+  "title": "Post Attempts",
+  "type": "integer"
+}

addedOutput schema / properties / tasks / items / properties / provider_idempotency_key

Added value: +{
+  "default": "",
+  "title": "Provider Idempotency Key",
+  "type": "string"
+}

addedOutput schema / properties / tasks / items / properties / recovery_attempts

Added value: +{
+  "default": 0,
+  "title": "Recovery Attempts",
+  "type": "integer"
+}

addedOutput schema / properties / tasks / items / properties / reference_sha256

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "title": "Reference Sha256",
+  "type": "array"
+}

addedOutput schema / properties / tasks / items / properties / safe_to_retry

Added value: +{
+  "default": false,
+  "title": "Safe To Retry",
+  "type": "boolean"
+}

changedOutput schema / properties / tasks / items / properties / status / enum

Previous value: -[
-  "queued",
-  "preparing",
-  "running",
-  "succeeded",
-  "failed",
-  "unknown",
-  "cancelled"
-]New value: +[
+  "queued",
+  "preparing",
+  "running",
+  "recovering",
+  "succeeded",
+  "failed",
+  "unknown",
+  "cancelled"
+]

First observedv0.2.1Oct 21, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses real behavior: queued/preparing/running states return normally while failed/unknown/cancelled return isError with full status retained. This status-handling contract is genuinely useful context an agent could not get from the annotations alone.

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?

Three short sentences with the core purpose and the no-resubmit constraint front-loaded, followed by status semantics and the checkpointer clarification. Dense but every sentence carries information; no filler.

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 an output schema present, return values needn't be spelled out, and the description still covers status/error behavior and the ambiguous checkpointer parameter. The main residual gap is that thread_id and limit are not described, though their schema constraints (default 100, min/max) carry much of that burden.

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 0%, so the description must carry parameter meaning; it explains task_ids filtering, cursor pagination, and clarifies that checkpointer is a local SQLite string namespace (not a path, object, or credential). It leaves limit and thread_id unexplained, and even uses 'next_cursor' while the schema parameter is 'cursor', so compensation is partial.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: query persisted tasks and absolute image paths, and the scope constraint 'does not resubmit upstream' distinguishes it from submit_image_tasks/retry_image_tasks. It does not explicitly name which sibling to use instead (e.g., wait_image_tasks or get_batch_result), so differentiation is implicit rather than stated.

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 tells you how to query (filter by task_ids or paginate via cursor) and that it doesn't resubmit upstream, which implies a read-only retrieval context. However, it gives no explicit when-to-use guidance relative to siblings like wait_image_tasks (poll until done) or get_batch_result, leaving the choice to inference.

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