Increase video resolution by upscaling from a public video URL using a selected model. Provide source URL and model ID to get a high-resolution version.
Upscale video ke resolusi lebih tinggi.
| Name | Required | Description | Default |
|---|---|---|---|
| model_id | Yes | ID model upscale-video | |
| video_url | Yes | URL http(s) publik video sumber (upload dulu dengan upload_file bila belum publik) | |
| parameters | No | Parameter tambahan sesuai input_schema model |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action ('upscale') and does not disclose whether the operation is asynchronous, consumes credits, returns a generation ID, or has any constraints such as file size or duration limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, direct sentence with no filler or redundant content. It is front-loaded with the core purpose and earns its place without unnecessary elaboration.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no output schema and no annotations, the description is too thin. It does not explain how to select a model, whether the process is asynchronous, or how to retrieve the result, despite siblings like get_generation_status and list_generations indicating such workflows exist.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the parameters model_id and video_url are already documented in the schema. The description adds no parameter-level meaning, but the baseline of 3 is appropriate since the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Upscale'), a clear resource ('video'), and the goal ('ke resolusi lebih tinggi' / to higher resolution). It clearly differentiates from sibling tools like upscale_image by targeting video, and from generate_video by being an upscaling operation rather than generation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no guidance on when to use this tool versus alternatives such as upscale_image or generate_video. It does not mention prerequisites, exclusions, or any context that would help an agent decide to invoke it rather than another tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.