MockClip

Vinted listings video

create_vinted_feed

Create a Vinted marketplace video (listing cards with photo, title, price and size, a heart that pops red when you like a listing, an item page with buy, offer and seller buttons, a hearts page with your saved items): listings that scroll and get hearted. Per feed screen (home) pass posts, where each post is one listing: name is the item title, handle the price (e.g. "£40"), text the size line (e.g. "Size 8"), mediaUrl the item photo and liked: true a filled heart; and a script of steps (scroll to a listing / offset / top / bottom, like = tap the listing's heart, pause). Texts and photos several screens share sit in one object each (listing, savedItems): an item page's title, details (one line per row: brand, category, size, condition, colour), description, uploaded line and buyNow label, and the saved items' photos as image URLs. flow walks through the app's screens (home, quickView, quickViewLiked, item, itemLiked, hearts, saved, savedUnliked) with push/pop/fade transitions; showTaps (default true) draws a touch indicator before each move. 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.

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_vinted_feed"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations only declare the generic mutation profile (readOnly false, destructive false, idempotent false), so the description carries real weight and delivers: free-plan exports carry a MockClip watermark, the free plan allows only 2 MCP renders, and the agent is told to surface an upgrade at /pricing. It also discloses that showTaps defaults to true. It does not cover export latency or failure modes, keeping it short of a 5.

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?

The purpose is front-loaded in the first clause, which is good, but the remainder is one sprawling sentence stitched together with parentheses, colons and semicolons. The dense parenthetical listing of screens and the long field-mapping clause would read far better as short bulleted lines.

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

Completeness5/5

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

For a 17-parameter, deeply nested, output-schemaless video generator, the description supplies what the schema cannot: the mental model of posts + script + flow + shared text objects, and the plan/watermark constraints that affect the result. The remaining parameters all carry their own schema descriptions, so nothing critical is left unexplained.

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 coverage is only 47% and the raw field names (name/handle/text on a post) are meaningless on their own; the description rescues them by mapping name=item title, handle=price, text=size line, mediaUrl=photo, liked=filled heart, and by explaining listing.details as one line per row (brand, category, size, condition, colour). Core creative parameters are therefore well explained, though theme, sceneId, videoFormat, exportFormat, exportQuality, soundSettings and composedPost get nothing beyond their schema text.

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?

States a specific verb and resource — "Create a Vinted marketplace video" — and then enumerates the concrete UI artifacts produced (listing cards with photo/title/price/size, popping heart, item page with buy/offer/seller, hearts page). That level of specificity makes it unmistakable versus siblings like create_x_feed or create_facebook_marketplace_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?

Usage is implied through the field-mapping instructions ("Per feed screen (home) pass `posts`", "a `script` of steps") and the plan-related note, but there is no explicit when-to-use / when-not-to-use statement and no sibling is named as an alternative. An agent must infer selection from the Vinted branding alone.

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?