MockClip

Uber Eats walkthrough video

create_uber_eats_feed

Create an animated Uber Eats walkthrough (a restaurant list to browse, store aisles of products, a checkout summary with editable totals, pages that scroll): screens that scroll one after another. Per screen (home, store, checkout) pass its text fields and row lists, plus script: scroll and pause steps (post is a stop on the page, offset a distance, to top or bottom). Leave script out for the usual scroll down the page, or pass [] to stay put. flow lists the screens in order; each plays its script before the next one. Fewer rows than the design's slots repeat to fill the page. Images must be public https URLs. 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_uber_eats_feed"
  }
}

Input Schema

Name	Required	Description
`flow`	No
`home`	No
`store`	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.
`checkout`	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.
`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
`showHomeIndicator`	No	Draw the iOS home indicator bar at the bottom of the screen (default true).

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedNov 7, 2026
- addedInput schema / properties / checkout / properties / addressDetail
```
Added value: +{
+  "maxLength": 200,
+  "type": "string"
+}
```
- addedInput schema / properties / checkout / properties / itemNote
```
Added value: +{
+  "maxLength": 200,
+  "type": "string"
+}
```
- addedInput schema / properties / checkout / properties / itemOptions
```
Added value: +{
+  "maxLength": 200,
+  "type": "string"
+}
```
- addedInput schema / properties / checkout / properties / suggestion1
```
Added value: +{
+  "maxLength": 200,
+  "type": "string"
+}
```
- addedInput schema / properties / checkout / properties / suggestion2
```
Added value: +{
+  "maxLength": 200,
+  "type": "string"
+}
```
- addedInput schema / properties / store / properties / aisle4
```
Added value: +{
+  "maxLength": 200,
+  "type": "string"
+}
```
- addedInput schema / properties / store / properties / aisle5
```
Added value: +{
+  "maxLength": 200,
+  "type": "string"
+}
```
- addedInput schema / properties / store / properties / aisle6
```
Added value: +{
+  "maxLength": 200,
+  "type": "string"
+}
```
- addedInput schema / properties / store / properties / promo
```
Added value: +{
+  "maxLength": 200,
+  "type": "string"
+}
```
AddedNov 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The annotations only declare the generic profile (not read-only, non-destructive, non-idempotent), and the description adds real operational facts: images must be public https URLs, free-plan exports carry a MockClip watermark, and the free plan is capped at 2 MCP renders. Those constraints, plus the instruction to surface the /pricing upgrade path, are exactly the behavior an agent cannot get from structured fields.

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?

It is dense and front-loaded: the output is described first, then per-screen payloads, then `script`/`flow` semantics, then constraints. The parenthetical screen inventory and the phrase 'screens that scroll one after another' restate each other slightly, and the upgrade note is verbose, but no sentence is pure 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 15-parameter, deeply nested, no-output-schema, non-idempotent render tool, the definition covers the flow/script core but omits what the call returns (a rendered file, a render job, a URL?) and says nothing about export duration, polling, or how long the 2 free renders take. Presentation controls handled elsewhere in the schema (videoFormat, sceneId, exportFormat) are left to their own field descriptions.

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 53% schema coverage, the description compensates well for the most important ambiguous parts: `script` step semantics (`post` as a page stop, `offset` as distance, `to` top/bottom), `flow` ordering where each screen plays its script before the next, and the rule that missing rows repeat into the design's slots. It leaves `theme`, `soundSettings`, `showTaps`, and most of the checkout fields unaddressed, but the highest-risk nested structures 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 (Create) and resource (an animated Uber Eats walkthrough) and enumerates the three screens it renders (home restaurant list, store aisles, checkout summary). An agent can tell it apart from chat-feed tools like create_doordash_feed only by implicit domain wording, since no sibling is named.

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 guidance is operational rather than selective: it says to omit `script` for the default scroll or pass `[]` to stay put, and it explains the free-plan path. It never states when to prefer this tool over the near-identical create_doordash_feed sibling, so routing still relies on inference from the brand name.

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?