Skip to main content
Glama

Reddit thread video

create_reddit_thread

Create a Reddit thread animation. All options controllable (nested comments supported). Images: every image field takes an https URL from an allowed host (see /integrations), or upload:<short-label> (e.g. upload:contact-avatar) when the user wants to use their own image — including one attached to this chat, which cannot be passed to tools. Never ask the user to host an image somewhere: the returned link asks them to add each upload: image from their device before it exports. Use the same label for the same image and a different label for a different one. Free-plan exports include a MockClip watermark and the free plan includes 2 MCP renders; if the caller is on the free plan, mention that they can upgrade at /pricing for watermark-free exports and more renders.

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": {
      "post": "<post>",
      "comments": "<comments>"
    },
    "name": "create_reddit_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
postYes
themeNo
sceneIdNoStage the clip on a scene instead of a flat frame. Overrides videoFormat and showBezel: the export takes the scene's aspect. Two kinds. 3D close-up — a 3D phone filmed by a camera that flies in close to each new message, card or banner as it appears, with depth of field and motion blur: "closeup" (9:16), "closeup-wide" (16:9). Hand-held — the clip composited onto real footage of a hand holding a phone, for a filmed look; vertical 9:16: "outdoors" (outdoors), "bookshelf" (bookshelf), "two-hands" (two hands), "on-desk" (on the desk), "dim-room" (dim room); landscape 16:9 (YouTube, presentations): "city-wide" (city), "desk-wide" (desk), "neon-wide" (neon), "studio-wide" (studio). Default: none.
commentsYes
showBezelNoDraw the iPhone bezel around the screen (default true). With 1:1 it frames the top of the phone; false gives a plain frame.
textScaleNoText size: a zoom of the phone UI (text, bubbles, avatars, bars, keyboard, notification banners) as a multiplier from 1 (default, the app's real size) to 1.5, in steps of 0.1 — use it when a short conversation or a single notification should fill the screen. Chat and notification apps only; the other apps ignore it.
videoFormatNoOutput aspect ratio. "1:1" is a square for feed posts: chat apps fit the conversation into the square, the other apps show the top of the screen (phone-call ignores it). "9:16", "9:19.5" (iPhone) and "3:2" apply with showBezel false. "16:9" (widescreen) is for the notification tools with background.backgroundType "floating" only, where the frame is a photo scene and any aspect ratio applies without a bezel; on any other clip it is ignored. Default: the iPhone bezel, 9:16.
exportFormatNoOutput file. "mp4" (default) and "gif" are opaque. "webm" (VP9) and "mov" (ProRes 4444, large files) keep an alpha channel: the only way a transparent background, or the corners around the phone bezel, stay transparent. With background.backgroundType "transparent" and no exportFormat the clip exports as webm. Transparent WebM / MOV export needs a Creator or Studio plan; on other plans the clip is made as mp4 and the reply says so.
exportQualityNoResolution and frame rate of the file: "720p" or "1080p" (Full HD) at 15, 24, 30 or 60 fps, e.g. "1080p-30". Default "720p-30". Full HD takes up to 4× as long to export; 60 fps about twice as long and needs a Creator or Studio plan — on other plans the clip is made at 30 fps and the reply says so.
showStatusBarNoDraw the iOS status bar (time, signal, battery) at the top of the screen (default true). Applies with showBezel false or a sceneId: inside the iPhone bezel the status bar is always drawn, so to remove it set showBezel false too.
soundSettingsNo
sceneBackgroundNoBackdrop behind the phone on a 3D close-up scene (sceneId "closeup" / "closeup-wide"): a colour as "#RRGGBB" — the backdrop is a soft gradient made from it, so a brand colour or a dark one both work — or "transparent" for the phone alone over an alpha channel, to lay over other footage (the clip then exports as webm unless exportFormat says otherwise; mp4 and gif cannot carry it and get the default backdrop). Default: a light blue. Ignored without a 3D close-up scene.
showHomeIndicatorNoDraw the iOS home indicator bar at the bottom of the screen (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / sceneBackground
      Added value: +{
      +  "description": "Backdrop behind the phone on a 3D close-up scene (sceneId \"closeup\" / \"closeup-wide\"): a colour as \"#RRGGBB\" — the backdrop is a soft gradient made from it, so a brand colour or a dark one both work — or \"transparent\" for the phone alone over an alpha channel, to lay over other footage (the clip then exports as webm unless exportFormat says otherwise; mp4 and gif cannot carry it and get the default backdrop). Default: a light blue. Ignored without a 3D close-up scene.",
      +  "pattern": "^(transparent|#[0-9a-fA-F]{6})$",
      +  "type": "string"
      +}
  2. Changed4 schema fields changed
    • changedInput schema / properties / sceneId / description
      Previous value: -"Composite the clip onto real footage of a hand holding a phone, for a filmed look. Overrides videoFormat and showBezel: the export takes the scene's aspect, with the footage around the phone. Vertical 9:16 scenes: \"outdoors\" (outdoors), \"bookshelf\" (bookshelf), \"two-hands\" (two hands), \"on-desk\" (on the desk), \"dim-room\" (dim room). Landscape 16:9 scenes (YouTube, presentations): \"city-wide\" (city), \"desk-wide\" (desk), \"neon-wide\" (neon), \"studio-wide\" (studio). Default: none."New value: +"Stage the clip on a scene instead of a flat frame. Overrides videoFormat and showBezel: the export takes the scene's aspect. Two kinds. 3D close-up — a 3D phone filmed by a camera that flies in close to each new message, card or banner as it appears, with depth of field and motion blur: \"closeup\" (9:16), \"closeup-wide\" (16:9). Hand-held — the clip composited onto real footage of a hand holding a phone, for a filmed look; vertical 9:16: \"outdoors\" (outdoors), \"bookshelf\" (bookshelf), \"two-hands\" (two hands), \"on-desk\" (on the desk), \"dim-room\" (dim room); landscape 16:9 (YouTube, presentations): \"city-wide\" (city), \"desk-wide\" (desk), \"neon-wide\" (neon), \"studio-wide\" (studio). Default: none."
    • changedInput schema / properties / sceneId / enum
      Previous value: -[
      -  "outdoors",
      -  "bookshelf",
      -  "two-hands",
      -  "on-desk",
      -  "dim-room",
      -  "city-wide",
      -  "desk-wide",
      -  "neon-wide",
      -  "studio-wide"
      -]New value: +[
      +  "closeup",
      +  "closeup-wide",
      +  "outdoors",
      +  "bookshelf",
      +  "two-hands",
      +  "on-desk",
      +  "dim-room",
      +  "city-wide",
      +  "desk-wide",
      +  "neon-wide",
      +  "studio-wide"
      +]
    • changedInput schema / properties / videoFormat / description
      Previous value: -"Output aspect ratio. \"1:1\" is a square for feed posts: chat apps fit the conversation into the square, the other apps show the top of the screen (phone-call ignores it). \"9:16\", \"9:19.5\" (iPhone) and \"3:2\" apply with showBezel false. Default: the iPhone bezel, 9:16."New value: +"Output aspect ratio. \"1:1\" is a square for feed posts: chat apps fit the conversation into the square, the other apps show the top of the screen (phone-call ignores it). \"9:16\", \"9:19.5\" (iPhone) and \"3:2\" apply with showBezel false. \"16:9\" (widescreen) is for the notification tools with background.backgroundType \"floating\" only, where the frame is a photo scene and any aspect ratio applies without a bezel; on any other clip it is ignored. Default: the iPhone bezel, 9:16."
    • changedInput schema / properties / videoFormat / enum
      Previous value: -[
      -  "9:16",
      -  "9:19.5",
      -  "3:2",
      -  "1:1"
      -]New value: +[
      +  "9:16",
      +  "9:19.5",
      +  "3:2",
      +  "1:1",
      +  "16:9"
      +]
  3. Changed1 schema field changed
    • addedInput schema / properties / textScale
      Added value: +{
      +  "description": "Text size: a zoom of the phone UI (text, bubbles, avatars, bars, keyboard, notification banners) as a multiplier from 1 (default, the app's real size) to 1.5, in steps of 0.1 — use it when a short conversation or a single notification should fill the screen. Chat and notification apps only; the other apps ignore it.",
      +  "maximum": 1.5,
      +  "minimum": 1,
      +  "type": "number"
      +}
  4. Changed3 schema fields changed
    • addedInput schema / properties / exportQuality
      Added value: +{
      +  "description": "Resolution and frame rate of the file: \"720p\" or \"1080p\" (Full HD) at 15, 24, 30 or 60 fps, e.g. \"1080p-30\". Default \"720p-30\". Full HD takes up to 4× as long to export; 60 fps about twice as long and needs a Creator or Studio plan — on other plans the clip is made at 30 fps and the reply says so.",
      +  "enum": [
      +    "720p-15",
      +    "720p-24",
      +    "720p-30",
      +    "720p-60",
      +    "1080p-15",
      +    "1080p-24",
      +    "1080p-30",
      +    "1080p-60"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / showHomeIndicator
      Added value: +{
      +  "description": "Draw the iOS home indicator bar at the bottom of the screen (default true).",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / showStatusBar
      Added value: +{
      +  "description": "Draw the iOS status bar (time, signal, battery) at the top of the screen (default true). Applies with showBezel false or a sceneId: inside the iPhone bezel the status bar is always drawn, so to remove it set showBezel false too.",
      +  "type": "boolean"
      +}
  5. Changed1 schema field changed
    • addedInput schema / properties / exportFormat
      Added value: +{
      +  "description": "Output file. \"mp4\" (default) and \"gif\" are opaque. \"webm\" (VP9) and \"mov\" (ProRes 4444, large files) keep an alpha channel: the only way a transparent background, or the corners around the phone bezel, stay transparent. With background.backgroundType \"transparent\" and no exportFormat the clip exports as webm. Transparent WebM / MOV export needs a Creator or Studio plan; on other plans the clip is made as mp4 and the reply says so.",
      +  "enum": [
      +    "mp4",
      +    "gif",
      +    "webm",
      +    "mov"
      +  ],
      +  "type": "string"
      +}
  6. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare this is a non-read-only, non-destructive, closed-world, non-idempotent creation call, and the description adds real behavioral context beyond that: free-plan exports carry a MockClip watermark, the free plan allows 2 MCP renders, and the returned link will prompt the user to add each `upload:` image from their device before export. It also implies a link is returned. It does not cover render time or failure behavior, but the plan/watermark/upload disclosure is substantive.

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

Conciseness5/5

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

The purpose is stated first, then the image-handling rules, then the plan/watermark note — a sensible front-load. Each sentence carries distinct operational information (label uniqueness, never ask the user to host, upgrade mention) with no filler.

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

Completeness4/5

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

For a 13-parameter tool with nested comment objects and no output schema, the description covers the hardest agent-facing problems: the `upload:` image workflow, what the returned link does, and plan-driven watermark/render limits. The rich per-parameter schema descriptions (sceneId, exportFormat, exportQuality, etc.) carry the rest, so remaining gaps are minor.

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 69%, and the description compensates by defining the image-value convention that the schema does not: every image field accepts an https URL from an allowed host or an `upload:<short-label>` token, with the rule to reuse the same label for the same image and a different label for a different one. That is meaningful semantics an agent cannot get from `format: uri` alone.

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 opens with a specific verb and resource ('Create a Reddit thread animation') and notes that nested comments are supported, which tells an agent exactly what artifact this produces and distinguishes it from the other app-specific create_* tools. It does not explicitly name a sibling or a boundary, but the resource is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The guidance present is about how to fill image fields (https URL from an allowed host vs `upload:<label>`, never ask the user to host an image) and when to mention the free-plan upgrade, which is genuinely useful. However, there is no when-to-use vs when-not-to-use guidance relative to the other create_* tools, so selection context is only implied by the app name.

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