Skip to main content
Glama
AceDataCloud

VeoMCP

by AceDataCloud
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

veo_get_tasks_batch

Retrieve status and video details for multiple video generation tasks at once. Reduces the need for repeated single-task queries.

Instructions

Query multiple video generation tasks at once.

Efficiently check the status of multiple tasks in a single request.
More efficient than calling veo_get_task multiple times.

Use this when:
- You have multiple pending generations to check
- You want to get status of several videos at once
- You're tracking a batch of generations

Returns:
    Status and video information for all queried tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOptional task type filter.
limitNoMaximum number of tasks to return.
offsetNoNumber of matching tasks to skip for list retrieval.
task_idsNoOptional list of task IDs to query. Maximum recommended batch size is 50 tasks.
trace_idsNoOptional list of trace identifiers to query.
created_at_maxNoReturn tasks created before this Unix timestamp.
created_at_minNoReturn tasks created after this Unix timestamp.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed12 schema fields changedv0.1.8
    • addedInput schema / properties / created_at_max
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Return tasks created before this Unix timestamp.",
+  "title": "Created At Max"
+}
    • addedInput schema / properties / created_at_min
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Return tasks created after this Unix timestamp.",
+  "title": "Created At Min"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 12,
+  "description": "Maximum number of tasks to return.",
+  "title": "Limit",
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Number of matching tasks to skip for list retrieval.",
+  "title": "Offset",
+  "type": "integer"
+}
    • addedInput schema / properties / task_ids / anyOf
      Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / task_ids / default
      Added value: +null
    • changedInput schema / properties / task_ids / description
      Previous value: -"List of task IDs to query. Maximum recommended batch size is 50 tasks."New value: +"Optional list of task IDs to query. Maximum recommended batch size is 50 tasks."
    • removedInput schema / properties / task_ids / items
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / task_ids / type
      Removed value: -"array"
    • addedInput schema / properties / trace_ids
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional list of trace identifiers to query.",
+  "title": "Trace Ids"
+}
    • addedInput schema / properties / type
      Added value: +{
+  "default": "",
+  "description": "Optional task type filter.",
+  "title": "Type",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "task_ids"
-]
  2. Addedv0.1.4
  3. Removedv0.1.3
  4. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description must carry the burden. It clearly frames the tool as a non-destructive 'query' operation, states that it returns status and video information, and emphasizes batch efficiency. It does not discuss auth, rate limits, or failure behavior, but the read-only intent is clear.

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?

The description is concise and front-loaded, with a clear opening statement and structured 'Use this when' bullets. It is slightly repetitive ('efficiently' appears in two sentences), but every section earns its place and supports quick scanning.

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?

Given the tool has seven optional parameters and an output schema, the description supplies the necessary overall behavior: batch status checking and returned video information. Parameter details are left to the schema, which is acceptable here because the schema descriptions are complete and meaningful.

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 description adds general context about querying multiple tasks, but it does not elaborate on each parameter. Schema description coverage is 100%, so every parameter already has a meaningful description; the tool text simply reinforces the batch-facing purpose.

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 uses a specific verb (query) and clearly identifies the resource (multiple video generation tasks), immediately distinguishing it from the single-task sibling veo_get_task. The phrase 'More efficient than calling veo_get_task multiple times' further clarifies its unique role.

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 provides explicit 'Use this when' scenarios, such as checking multiple pending generations or tracking a batch. It also names the alternative veo_get_task and explains when this batch variant is preferable, giving clear usage boundaries.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AceDataCloud/VeoMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server