MockClip

Telegram conversation video

create_telegram_conversation

Create a Telegram conversation animation (reply quotes, image attachments with file name and size, sent/read check marks, typing indicator, an on-screen keyboard that slides up while you type, 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, calls): pass flow (screen steps with push/pop/tab/peek transitions), chatList rows, calls rows; without them the clip shows the conversation only. keyboard shows the on-screen keyboard while the user types (auto), always, or never. 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
`flow`	No
`calls`	No
`group`	No
`theme`	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.
`chatList`	No
`keyboard`	No
`messages`	Yes
`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.
`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.
`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 already declare the write/non-destructive/non-idempotent profile, so the bar is lower. The description adds genuine behavioral context beyond them: free-plan exports carry a MockClip watermark, the free plan includes only 2 MCP renders, and the caller should mention /pricing upgrade. It does not contradict any annotation.

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 what the tool produces, then descends into optional parameters. The single dense paragraph is long and the opening feature list is packed, but each sentence roughly earns its place and nothing is redundant padding.

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

Completeness3/5

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

For a 19-parameter, deeply nested tool with no output schema and 42% schema coverage, the description covers the core creative flows well but omits many tunable parameters (theme, export/format, sound, status bar). An agent can call it correctly for the common case but must fall back on the schema for much of the configuration surface.

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

Parameters3/5

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

Schema description coverage is only 42% across 19 params, so the description carries more burden. It adds real meaning for `flow`, `keyboard`, and especially `group.members`/`author` (contactName becomes the group name, use at least three different authors), but leaves theme, videoFormat use, exportQuality, soundSettings and others unaddressed where the schema is silent.

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 Telegram conversation animation") and the platform name inherently distinguishes it from the many sibling create_*_conversation tools. The following feature list (reply quotes, attachments, sent/read checks, typing indicator, keyboard) makes the output concrete rather than generic.

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?

Gives clear conditional guidance on optional features: without `flow`/`chatList`/`calls` the clip shows the conversation only, and `keyboard` has auto/always/never behavior. It explains the group-chat variant and the free-plan scenario, but never names an alternative sibling or states when NOT to use this tool, so it stops short of full routing 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?