MockClip

Incoming phone call video

create_phone_call

Create a full-screen phone call animation. 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
`theme`	No
`outcome`	Yes
`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.
`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.
`callerName`	Yes
`delayBefore`	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.
`callerNumber`	No
`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.
`ringDuration`	No
`endedDuration`	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
`callerAvatarUrl`	No
`connectedDuration`	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

C2.7/5.0

Behavior3/5

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

Annotations already state this is a non-read-only, non-idempotent, non-destructive generator. On top of that the description adds genuinely useful behavior: free-plan exports carry a MockClip watermark and the free plan is limited to 2 MCP renders. However, it says nothing about generation latency, output delivery, or how partial-option combinations (e.g. transparent export requiring a paid plan) affect results — details that live only in the schema.

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

Conciseness2/5

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

Good front-loading of the core action, but 'All options controllable' is a wasted sentence and the third sentence is a long marketing/upgrade instruction aimed at the end user rather than at an agent selecting the tool. It occupies roughly half the description without helping correct invocation.

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

Completeness2/5

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

For a rich generation tool with 18 parameters, a nested object, no output schema and 44% schema coverage, the description is far too thin. It covers plan limits but omits parameter meaning, output characteristics, and prerequisites such as paid-plan requirements for transparent or 60fps exports.

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

Parameters2/5

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

With 18 parameters and only 44% schema description coverage, the description should carry real weight, but 'All options controllable' is filler and no parameter is mentioned. Parameters like callerName, outcome, delayBefore, ringDuration, endedDuration and soundSettings are explained in neither the description nor the schema.

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 full-screen phone call animation.' That clearly separates it from the text-chat and notification siblings, though it never explicitly distinguishes itself from create_phone_call_notification, which is the closest neighbor and could be confused with it.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no alternative tool is named. The only routing-like content is a plan/upgrade policy for watermarks and renders, which is billing messaging rather than tool-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?