Skip to main content
Glama

ninerouter_extend_video

Submit a source video to create a video extension job, enabling continued or longer generation through the 9Router MCP gateway.

Instructions

Submit an extension job using a source video.

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": {
      "request": "<request>"
    },
    "name": "ninerouter_extend_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNo
requestYesNative 9Router video fields, such as prompt, duration, image or video.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true, readOnlyHint=false and idempotentHint=false, so the bar for added context is modest, yet the description adds nothing. It does not say the call returns a job handle, whether the job is asynchronous, how long extension takes, or that results must be fetched separately. That leaves the actual workflow opaque.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is tight and front-loaded with the verb, so there is no wasted wording. The problem is under-specification rather than verbosity: one short sentence is not enough for a nested-payload, asynchronous job-submission tool.

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?

With no output schema and a free-form nested `request` object, the description carries most of the explanatory burden and does not meet it. An agent knows roughly what the tool does but not what the payload should contain or how to retrieve the resulting video, which is essential for a job-based operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: the nested `request` object has a one-line description, but `model` is undocumented in both schema and description. The description adds no meaning to either parameter, so it fails to compensate for the coverage gap on a nested free-form object.

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

Purpose3/5

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

The description gives a verb ("Submit") and a resource ("extension job") plus a hint about input ("using a source video"), so the general action is graspable. However, "extension job" is never explained and nothing distinguishes it from siblings like ninerouter_edit_video or ninerouter_generate_video, which an agent would plausibly confuse with it.

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 when-to-use guidance, no exclusion of alternatives, and no prerequisites. The agent is left to guess whether this is the right tool versus edit_video or generate_video, and no follow-up path (e.g. polling via video_status) is mentioned.

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