Skip to main content
Glama

ninerouter_edit_video

Submit a video editing job using a source video and native fields like prompt, duration, or image. Use it to request edits through the 9Router MCP gateway.

Instructions

Submit an edit 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_edit_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.7/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true, readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety and mutability profile is covered. The description adds almost nothing beyond that: it implies an asynchronous job but never says so explicitly, and says nothing about polling, cost, rate limits, or that resubmitting may create duplicate jobs.

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?

A single front-loaded sentence with zero filler, so nothing can be cut. The terseness is a coverage problem rather than a conciseness problem, which is scored elsewhere.

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

Completeness2/5

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

With no output schema, a nested free-form request object, and no parameter documentation, the description should explain the async job model and the request payload shape. Instead it is one sentence that leaves an agent unable to construct a correct edit request without guessing at the request fields.

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 description coverage is only 50%, so the description needs to compensate, and it does not. The 'model' parameter is a bare string with no description, and 'request' is a free-form object whose accepted fields (prompt, duration, image, video) are only vaguely gestured at in the schema; the description mentions no parameters at all.

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 gives a specific verb and resource: 'Submit an edit job using a source video.' That is clearer than a tautology and tells the agent the input is an existing video. It does not distinguish this from siblings such as ninerouter_generate_video or ninerouter_extend_video, which is exactly the gap that keeps it at 4 rather than 5.

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 guidance on when to choose video editing over generation, extension, or status polling. The presence of ninerouter_video_status as a sibling makes the missing 'then poll for status' instruction a notable omission. Nothing tells the agent what prerequisites (e.g., an existing video asset) are required.

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