MockClip

Messenger conversation video

create_facebook_messenger_conversation

Create a Messenger conversation animation (photo grids, sent/read check marks, the contact's avatar as the read mark, typing indicator, date separators, an on-screen keyboard that slides up while you type, a three-dot typing bubble in the thread, a name and avatar on every message, so a channel has many people, group chats with a name and avatar per member). Optionally walk through the app's screens (chats, chat, people, discover, settings, profile, newMessage, call, videoCall, camera, story, actions, gifs): pass flow (screen steps with push/pop/tab/fade/modal/dismiss/sheet/swipe transitions), chatList rows, per-screen objects (people, discover, settings, profile, newMessage, call, videoCall, camera, story, actions, gifs); without them the clip shows the conversation only. keyboard shows the on-screen keyboard while the user types (auto), always, or never. showTaps (default true) draws a touch indicator where the user taps before each screen change. The first message is stamped with a date line (its dateLabel, else its timestamp, else TODAY; firstDateLine: false hides it). stories rows draw a story ring unless hasStory: false. A story step takes params: { story: n } — the strip bubble that is tapped (1 = first person); the story shows that person's name and avatar. group.members (2–12 names, optional avatarUrl) makes the thread a group chat: contactName is the group's name and each "other" message's author names the member who wrote it — use at least three different authors. 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
`call`	No
`flow`	No
`gifs`	No
`group`	No
`intro`	No
`story`	No
`theme`	No
`camera`	No
`people`	No
`profile`	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.
`stories`	No
`chatList`	No
`discover`	No
`keyboard`	No
`messages`	Yes
`settings`	No
`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.
`videoCall`	No
`newMessage`	No
`contactName`	Yes
`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.
`contactStatus`	No
`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.
`firstDateLine`	No
`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
`contactAvatarUrl`	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"
+}

Changed3 schema fields changedOct 8, 2026

addedInput schema / properties / group

Added value: +{
+  "properties": {
+    "members": {
+      "items": {
+        "properties": {
+          "avatarUrl": {
+            "format": "uri",
+            "maxLength": 2000,
+            "type": "string"
+          },
+          "name": {
+            "maxLength": 80,
+            "minLength": 1,
+            "type": "string"
+          }
+        },
+        "required": [
+          "name"
+        ],
+        "type": "object"
+      },
+      "maxItems": 12,
+      "minItems": 2,
+      "type": "array"
+    }
+  },
+  "required": [
+    "members"
+  ],
+  "type": "object"
+}

addedInput schema / properties / messages / items / properties / author

Added value: +{
+  "maxLength": 80,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / messages / items / properties / authorAvatarUrl

Added value: +{
+  "format": "uri",
+  "maxLength": 2000,
+  "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 declare it as a non-read-only, non-destructive create with no idempotency, so the description carries real weight by disclosing free-plan gating (watermark, 2 renders) and instructing the agent to surface the /pricing upgrade path. It also states defaults like showTaps=true, adding behavior beyond the annotations.

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?

Nearly all content is compressed into one sprawling paragraph that mixes required behavior, optional features, and plan messaging. Each clause carries distinct information, so little is pure waste, but the lack of bullets or front-loaded grouping makes it harder to scan than it needs to be.

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 32-parameter nested renderer with no output schema, the description covers the highest-complexity surfaces (flow, group, keyboard, story, date line) and the plan caveat. It stops short of documenting many secondary screen objects, but is largely sufficient to invoke the tool correctly.

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?

With only 25% schema description coverage across 32 params, the description compensates well by explaining flow steps and transitions, group.members semantics (2-12, contactName as group name, author naming, at-least-three-authors rule), keyboard modes, firstDateLine fallback chain, and story params. Many nested objects (people, discover, settings, profile, newMessage) remain undocumented, so it is not fully exhaustive.

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?

Opens with a specific verb+resource ('Create a Messenger conversation animation') and immediately names distinguishing capabilities (photo grids, read marks, typing bubble). The Messenger product name separates it cleanly from the many chat-app siblings such as create_imessage_conversation, create_whatsapp_conversation and create_telegram_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?

The bulk of the text explains how to configure the tool rather than when to choose it. Usage is implied by the product-specific name and by the statement that omitting flow/chatList yields the conversation-only clip, but there is no explicit when-to-use, prerequisite, or alternative-tool 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?