Skip to main content
Glama

Upscale a video

upscale_video

Upscale a clip to 1080p or 4k: more detail, same motion and length. Credits are taken only when the upscaled clip is delivered; it is saved as a new clip in the library. Spends the account's PrismPoster credits at the same price as on prismposter.com (quote_job prices it first, free). When the person must decide something first (a price above their ask-first amount, consent for real people in pictures, the right to use a clip), it returns approval_required and nothing runs until they answer in PrismPoster's card or at the link. Everything made is saved to their PrismPoster library. Requests involving anyone under 18 or depicting public figures or office holders are refused before any charge.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "upscale_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNoThe size to upscale it to.
clip_idNoThe clip to work on: one PrismPoster made, as a clip_id from get_job or a video asset_id from list_library.
approval_idNoOnly after an approval_required answer: the approval_id it returned, once the person has answered. The job then runs exactly as they approved it and the other arguments are ignored.
idempotency_keyNoOptional. A unique key for this job (8-128 letters, digits, . _ : -). Repeating a call with the same key returns the first call's job instead of starting and charging a second one, so set it whenever a retry is possible.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / target / description
      Previous value: -"The size to sharpen it to."New value: +"The size to upscale it to."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only give coarse safety hints; the description adds the critical economics and workflow: credits charged only on delivery, price matched to prismposter.com, output saved as a new clip, approval_required halting execution until answered, and pre-charge refusals for minors and public figures. That is exactly the behavioral context an agent needs before spending money.

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?

Front-loaded with the core action and outcome, then the cost/approval rules. Slightly long and has mild redundancy between 'it is saved as a new clip in the library' and 'Everything made is saved to their PrismPoster library,' but every other sentence carries decision-relevant information.

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

Completeness5/5

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

For a 4-parameter mutation with no output schema, it covers the full lifecycle: selection of target/clip, credit pricing and charging timing, approval interrupts, output persistence, and policy refusals. An agent can call this correctly and understand the consequences without further context.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3, but the description adds workflow meaning: approval_required as a possible return, the fact that an approval_id makes the job run 'exactly as they approved' with other args ignored, and the role of quote_job before spending credits. That is useful beyond the schema's field-level text.

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 ('Upscale a clip') plus the outcome ('more detail, same motion and length'), which cleanly separates it from siblings like change_video, extend_video, and edit_image. The two target resolutions are named explicitly.

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?

Explains the decision flow (quote_job prices it first, free; approval_required when a person must decide) and when requests are refused. It does not explicitly compare against siblings such as change_video, but the upscale-specific context is clear enough to select it correctly.

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