Skip to main content
Glama
Sign In
infinitetalk-mcp

infinitetalk-mcp

by runapi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_task

Fetch the current status and result payload for an InfiniteTalk audio-to-video task using its task ID.

Instructions

Fetch the current status and latest result payload for a infinitetalk task.

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
actionNoAsynchronous endpoint the task was created on. Defaults to the line's only asynchronous endpoint.
task_idYesTask id returned when the task was created.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changedv0.1.7
    • changedInput schema / properties / action / description
      Previous value: -"Endpoint the task was created on. Defaults to the line's only endpoint."New value: +"Asynchronous endpoint the task was created on. Defaults to the line's only asynchronous endpoint."
  3. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose that the operation is a read ('Fetch') and that it returns the 'latest' result payload, which distinguishes it from a full-history fetch, but it says nothing about auth requirements, error/terminal states, result expiry, or whether repeated calls are safe.

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?

A single front-loaded sentence with zero filler; the verb and returned data are stated immediately. Nothing redundant or restating the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description is the only source of return-value framing. It names status and result payload, which is a reasonable minimum, but leaves polling behavior, terminal states, and error handling unspecified for an async-task status 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 task_id and the action enum are already fully documented in the schema. The description adds no additional meaning about either parameter, which is the expected baseline 3 when the schema does the heavy lifting.

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?

The description states a specific verb ('Fetch') and resource ('status and latest result payload for a infinitetalk task'), so an agent knows exactly what the call returns. It does not explicitly differentiate itself from siblings like audio_to_video, but the resource is unambiguous.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no note that this is the polling counterpart to audio_to_video, and no advice on polling cadence or when to stop polling. The usage is only implied by the word 'status' and the async-task framing.

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

Deploy Server

Other Tools