Skip to main content
Glama

MockClip

by com.mockclip
OverviewDiscussionsAdmin

WhatsApp conversation video

create_whatsapp_conversation

Create a WhatsApp conversation animation. keyboard shows the on-screen keyboard while the user types (auto, the default), 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

NameRequiredDescriptionDefault
groupNo
themeNo
sceneIdNoComposite 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.
keyboardNo
messagesYes
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.
contactNameYes
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. 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.
contactStatusNo
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
contactAvatarUrlNo
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 / 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"
+}
  2. 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"
+}
  3. 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"
+}
  4. Changed3 schema fields changed
    • 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"
+}
  5. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations mark this as non-read-only, non-destructive, non-open-world, non-idempotent but say nothing about plan gating. The description adds genuinely useful behavior beyond that: free-plan exports carry a MockClip watermark, the free plan permits only 2 MCP renders, and the agent is told to surface the /pricing upgrade path. It stops short of render time or async/return behavior, but with annotations carrying the safety profile this is solid added context.

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?

Purpose is front-loaded in the first sentence, followed by per-parameter clarifications. Sentences are dense but earn their place; the trailing free-plan/upgrade instruction is slightly verbose but conveys an actionable instruction rather than filler.

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 16-parameter tool with nested objects and no output schema, the description covers only the group and keyboard dimensions plus plan gating. Many message-level timing/visual params (reactionDelay, typingSpeed, showReadCheck, etc.) are neither described here nor fully covered by the schema, leaving real gaps for an agent constructing a rich animation.

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 50% across 16 params, so the description must compensate. It explains the `keyboard` enum semantics, the `group.members` structure (2–12 names, optional avatarUrl), the meaning of `contactName` in group mode, and the non-obvious `author` convention ('use at least three different authors') that is absent from the schema. Timing, reaction, and check-mark params are left unexplained, but the highest-value parameters are covered.

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 first sentence gives a specific verb and resource ('Create a WhatsApp conversation animation'), which an agent can map to the WhatsApp sibling among the many platform-specific chat tools. The additional detail on keyboard and group behavior sharpens the purpose, but the description never explicitly contrasts itself with e.g. create_telegram_conversation or create_imessage_conversation, so differentiation rests mostly on the name.

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 through conditional guidance: 'keyboard' values, and 'group.members ... makes the thread a group chat' with 'use at least three different authors.' There is no explicit when-to-use-this vs an alternative tool statement or any exclusion. The free-plan note is a usage constraint but not a selection guideline.

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

All MockClip toolsInspect
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