Skip to main content
Glama

Add a still image to a long video

add_still

Puts a still image over a long-form project while the voice carries on, pinned to the transcript: it appears as the word at is said and goes with until, by default at the end of its sentence (8 s at most; 20 s with until). at_seconds and until_seconds take moments in the finished video instead and are turned into words once. placement: full (default, covers everything), screen (the screen's box, the camera bubble stays on top), inset (a rounded box in a corner) or split (the frame halved, the camera on one side and the image on the other; the screen recording isn't shown). It pushes in slowly and fades by default (an inset holds still). The image is asset_id from the brand kit, image_url (a ClipLaunch image link or a public https image the person gave you or owns), image_file (ChatGPT only: the image the person attached) or upload: true, for the person's own picture that is not on ClipLaunch yet: the still waits, and the reply has upload_url to give them and upload_post_url for your code sandbox (one image, valid an hour). PNG, JPEG or WebP, up to 20 MB, at least 480 pixels on its shorter side. Free. Returns still_id, status (ready, hidden with the reason, or needs_upload), start_seconds and end_seconds, the words it is pinned to, how the image fits and what to do next.

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": {
      "project_id": "<project_id>"
    },
    "name": "add_still"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoThe word it appears on, { take_id, word } from get_transcript
fitNoauto (default) fills its box when that keeps three quarters of the image, else shows it whole over a blurred copy; fill crops; whole shows all of it
fadeNoSeconds of fade in and out: 0 for a cut, or 0.1 to 0.5; default 0.3. A split doesn't fade
moveNoin (a slow push from 100% to 110%), out, or none; default in, none for an inset
sideNoplacement split only: the half the still takes; default left
focusNoThe point of the image to push towards and crop around, 0 to 1 each way; default the centre
insetNoplacement inset only: its corner and width (0.2 to 0.5 of the frame); default a corner clear of the presenter, 0.35
untilNoThe word it goes with; leave out (or null) for the default: the end of its sentence, at most 8 s
uploadNotrue: the person gives their own picture. The still is saved waiting, and you get upload_url for them (valid an hour). false is the same as leaving it out
asset_idNoAn image in the brand kit (get_brand lists its asset ids): the project's kit, or brand_id's
brand_idNoThe kit asset_id is in; default the project's
image_urlNoA ClipLaunch image link (a generate_assets stored_url, a compose_asset URL, a get_brand view_url), or a public https image the person gave you or owns. Fetched once, now
placementNofull (default) covers the frame; screen fills the screen's box under the camera bubble; inset is a rounded 16:9 box in a corner; split halves the frame, the camera on one side and the still on the other (the screen recording isn't shown)
at_secondsNoOr the moment in the finished video (what review_render shows), turned into the word playing then
image_fileNoChatGPT only: the image the person attached, as a list of one. Leave out in other apps
project_idYesFrom create_project
until_secondsNoOr the moment in the finished video it goes, turned into the last word started by then

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / image_file
      Added value: +{
      +  "description": "ChatGPT only: the image the person attached, as a list of one. Leave out in other apps",
      +  "items": {
      +    "properties": {
      +      "download_url": {
      +        "maxLength": 4096,
      +        "type": "string"
      +      },
      +      "file_id": {
      +        "maxLength": 200,
      +        "type": "string"
      +      },
      +      "file_name": {
      +        "maxLength": 255,
      +        "type": "string"
      +      },
      +      "mime_type": {
      +        "maxLength": 100,
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "download_url",
      +      "file_id"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 1,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • addedInput schema / properties / upload
      Added value: +{
      +  "description": "true: the person gives their own picture. The still is saved waiting, and you get upload_url for them (valid an hour). false is the same as leaving it out",
      +  "type": "boolean"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the tool is free, explains the upload wait flow and one-hour URLs, states image format/size constraints, and lists the returned fields. These are useful operational details that materially help an agent call and handle the tool correctly.

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?

The description is front-loaded and every major clause serves the 17-parameter workflow, so its length is largely justified. However, it is a dense run-on paragraph with some repetition of schema details, so it is not maximally concise or structured.

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?

Given 17 parameters, nested objects, and no output schema, the definition covers the essential behavior: timing, placement, motion, image sources, upload flow, constraints, and return fields. An agent has enough information to invoke it correctly and interpret the response.

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 coverage is 100%, so the baseline is 3, but the description adds workflow meaning around at/until pinning, at_seconds/until_seconds conversion, placement effects, default timing, and image-source alternatives. It does not fully resolve how multiple image sources interact, keeping it at 4 rather than 5.

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?

The description opens with a specific verb and resource: it puts a still image over a long-form project while the voice continues, pinned to the transcript. That is enough to distinguish it from sibling tools such as add_graphic or add_scene without opening their schemas.

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?

It clearly establishes the usage context: long-form projects, voice continuing, transcript-based timing, and image sources. It does not explicitly name alternatives or when not to use this tool versus add_graphic or animate_image, so it falls short of a 5.

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