Skip to main content
Glama

Get task

get_task
Read-only

Status of a make_screen_scene, place_screen (clip) or join_clips task. With wait_seconds, waits until it finishes. Once completed it gives the tool's full result: video_url, preview_url, and for place_screen the checks to act on. Calling the tool again with the same arguments returns the same task, so poll here instead.

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": {
      "task_id": "<task_id>"
    },
    "name": "get_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
wait_secondsNoMost agent clients stop waiting for a reply after about 60s

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Goes beyond readOnlyHint=true by disclosing idempotency (same arguments return the same task) and blocking behavior with wait_seconds. It also compensates for the absent output schema by naming the payload fields returned (video_url, preview_url, place_screen checks). It does not describe failure/error states or what a still-pending status looks like.

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 tight sentences, front-loaded with the scope line before the wait behavior and the polling advice. The small parenthetical "(clip)" and the trailing polling note are the only slightly loose elements; nothing is redundant.

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 two-parameter polling tool with no output schema and only a readOnly annotation, the description supplies the return shape, blocking semantics, and idempotency. The remaining gap is failure/expiry handling for task_id, which an agent would need for robust polling loops.

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 50%: wait_seconds is documented in the schema, including the 60s client-timeout caution, and the description reinforces that it waits until finish. task_id is undocumented in both places, though the description implies its origin via the named producer tools. That roughly meets the baseline given partial coverage.

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?

States a specific verb and resource ("Status of a ... task") and enumerates exactly which task-producing tools it covers: make_screen_scene, place_screen, join_clips. This lets an agent separate it from generic job siblings like check_jobs or get_render without opening any 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?

Explicitly tells the agent to poll this tool rather than re-invoking generation tools ("poll here instead") and explains the wait_seconds shortcut for blocking until completion. It stops short of stating what to do when a task fails or how this differs from check_jobs, so guidance is clear but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources