MockClip

Gemini chat video

create_gemini_conversation

Create a Gemini conversation animation (replies revealed from top to bottom, a thinking animation before each reply, the reply's action row and disclaimer, your message typed on the keyboard, the side drawer with your chats): each messages turn is the user's (typed into the input bar with the keyboard up, then sent — typed: false makes it appear at once) or the assistant's (a thinking animation for thinkingDuration seconds with an optional thinkingLabel, then the reply is revealed from top to bottom at streamingSpeed chars/s (default 100), then the action row fades in; error fails the reply instead). Replies keep their blank lines; lines starting with "* " or "- " draw as bullet points. A new chat opens on the home screen: the first message is typed there, and the conversation's title appears halfway through the first thinking phase. title is the conversation's title, placeholder the input bar's hint, sourceLabel the label beside the logo ("" hides it), disclaimer the line under the last reply ("" hides it), keyboard auto / always / never. Other screens take their texts / rows by screen id (home, drawer). flow walks through the app's screens (chat, home, drawer) with fade / drawer / push / pop transitions; showTaps (default true) draws a touch indicator before each move. All options controllable. 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.

Input Schema

Name	Required	Description
`flow`	No
`home`	No
`theme`	No
`title`	No
`drawer`	No
`sceneId`	No	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.
`keyboard`	No
`messages`	Yes
`showTaps`	No
`showBezel`	No	Draw the iPhone bezel around the screen (default true). With 1:1 it frames the top of the phone; false gives a plain frame.
`textScale`	No	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.
`disclaimer`	No
`placeholder`	No
`sourceLabel`	No
`videoFormat`	No	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.
`exportFormat`	No	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.
`exportQuality`	No	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.
`showStatusBar`	No	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.
`soundSettings`	No
`thinkingLabel`	No
`showHomeIndicator`	No	Draw the iOS home indicator bar at the bottom of the screen (default true).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 11, 2026

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"
+}

Changed3 schema fields changedOct 11, 2026

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"
+}

Changed1 schema field changedOct 11, 2026

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"
+}

First observedOct 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations only give the generic safety profile (not destructive, not idempotent, not open-world), so the description carries real weight here. It discloses plan-gated behaviour beyond the schema: free-plan exports carry a MockClip watermark and the free plan includes only 2 MCP renders. It does not describe runtime/latency expectations, but coverage of limits and upsell conditions is well above average.

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

Conciseness3/5

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

The core purpose is front-loaded, but the body is a single ~270-word paragraph with three levels of nested parentheses and colons, which makes it hard to scan. Most sentences carry real information, so it is dense rather than padded, but the structure is clearly suboptimal for a 21-parameter tool.

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 complex tool with 21 parameters, nested objects, 6 enums, no output schema and thin annotations, the description covers the required 'messages' surface thoroughly plus flow, screens, keyboard, taps and plan limits. It never explains the export pipeline or return value (no output schema), but it does disclose that some features silently downgrade on lower plans, which is the key completeness detail an agent needs.

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 only 38% across 21 parameters, so the description must compensate, and it does: it explains messages semantics (typed, thinkingDuration, thinkingLabel, streamingSpeed default 100, error, showActions), title/placeholder/sourceLabel/disclaimer, keyboard modes, flow transitions, showTaps default, and the home/drawer screen params. Bullet-point line handling is extra value the schema does not carry. Uncovered optional params (theme, soundSettings, delayBefore, typingSpeed) keep it from a 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?

States a specific verb and resource — 'Create a Gemini conversation animation' — and immediately enumerates the observable behaviours it produces (replies revealed top-to-bottom, thinking animation, keyboard typing). The Gemini branding plus the animation framing cleanly separates it from sibling conversation tools like create_chatgpt_conversation and create_imessage_conversation.

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?

Usage is implied by the app-specific name and description (this is the Gemini-flavoured chat render), but the definition never states when to pick this over a sibling such as create_chatgpt_conversation. The only explicit caller instruction is a plan/upsell nudge ('mention that they can upgrade at /pricing'), which is a sales hint rather than selection guidance.

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

All MockClip tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?