Skip to main content
Glama

Messenger conversation video

create_facebook_messenger_conversation

Create a Messenger conversation animation (photo grids, sent/read check marks, the contact's avatar as the read mark, typing indicator, date separators, an on-screen keyboard that slides up while you type, a three-dot typing bubble in the thread, 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, people, discover, settings, profile, newMessage, call, videoCall, camera, story, actions, gifs): pass flow (screen steps with push/pop/tab/fade/modal/dismiss/sheet/swipe transitions), chatList rows, per-screen objects (people, discover, settings, profile, newMessage, call, videoCall, camera, story, actions, gifs); without them the clip shows the conversation only. keyboard shows the on-screen keyboard while the user types (auto), always, or never. showTaps (default true) draws a touch indicator where the user taps before each screen change. The first message is stamped with a date line (its dateLabel, else its timestamp, else TODAY; firstDateLine: false hides it). stories rows draw a story ring unless hasStory: false. A story step takes params: { story: n } — the strip bubble that is tapped (1 = first person); the story shows that person's name and avatar. 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. Images: every image field takes an https URL from an allowed host (see /integrations), or upload:<short-label> (e.g. upload:contact-avatar) when the user wants to use their own image — including one attached to this chat, which cannot be passed to tools. Never ask the user to host an image somewhere: the returned link asks them to add each upload: image from their device before it exports. Use the same label for the same image and a different label for a different one. 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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "contactName": "<contactName>",
      "messages": "<messages>"
    },
    "name": "create_facebook_messenger_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
callNo
flowNo
gifsNo
groupNo
introNo
storyNo
themeNo
cameraNo
peopleNo
profileNo
sceneIdNoStage the clip on a scene instead of a flat frame. Overrides videoFormat and showBezel: the export takes the scene's aspect. Two kinds. 3D close-up — a 3D phone filmed by a camera that flies in close to each new message, card or banner as it appears, with depth of field and motion blur: "closeup" (9:16), "closeup-wide" (16:9). Hand-held — the clip composited onto real footage of a hand holding a phone, for a filmed look; vertical 9:16: "outdoors" (outdoors), "bookshelf" (bookshelf), "two-hands" (two hands), "on-desk" (on the desk), "dim-room" (dim room); landscape 16:9 (YouTube, presentations): "city-wide" (city), "desk-wide" (desk), "neon-wide" (neon), "studio-wide" (studio). Default: none.
storiesNo
chatListNo
discoverNo
keyboardNo
messagesYes
settingsNo
showTapsNo
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.
videoCallNo
newMessageNo
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. "16:9" (widescreen) is for the notification tools with background.backgroundType "floating" only, where the frame is a photo scene and any aspect ratio applies without a bezel; on any other clip it is ignored. 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.
firstDateLineNo
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
sceneBackgroundNoBackdrop behind the phone on a 3D close-up scene (sceneId "closeup" / "closeup-wide"): a colour as "#RRGGBB" — the backdrop is a soft gradient made from it, so a brand colour or a dark one both work — or "transparent" for the phone alone over an alpha channel, to lay over other footage (the clip then exports as webm unless exportFormat says otherwise; mp4 and gif cannot carry it and get the default backdrop). Default: a light blue. Ignored without a 3D close-up scene.
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 / sceneBackground
      Added value: +{
      +  "description": "Backdrop behind the phone on a 3D close-up scene (sceneId \"closeup\" / \"closeup-wide\"): a colour as \"#RRGGBB\" — the backdrop is a soft gradient made from it, so a brand colour or a dark one both work — or \"transparent\" for the phone alone over an alpha channel, to lay over other footage (the clip then exports as webm unless exportFormat says otherwise; mp4 and gif cannot carry it and get the default backdrop). Default: a light blue. Ignored without a 3D close-up scene.",
      +  "pattern": "^(transparent|#[0-9a-fA-F]{6})$",
      +  "type": "string"
      +}
  2. Changed4 schema fields changed
    • changedInput schema / properties / sceneId / description
      Previous value: -"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."New value: +"Stage the clip on a scene instead of a flat frame. Overrides videoFormat and showBezel: the export takes the scene's aspect. Two kinds. 3D close-up — a 3D phone filmed by a camera that flies in close to each new message, card or banner as it appears, with depth of field and motion blur: \"closeup\" (9:16), \"closeup-wide\" (16:9). Hand-held — the clip composited onto real footage of a hand holding a phone, for a filmed look; vertical 9:16: \"outdoors\" (outdoors), \"bookshelf\" (bookshelf), \"two-hands\" (two hands), \"on-desk\" (on the desk), \"dim-room\" (dim room); landscape 16:9 (YouTube, presentations): \"city-wide\" (city), \"desk-wide\" (desk), \"neon-wide\" (neon), \"studio-wide\" (studio). Default: none."
    • changedInput schema / properties / sceneId / enum
      Previous value: -[
      -  "outdoors",
      -  "bookshelf",
      -  "two-hands",
      -  "on-desk",
      -  "dim-room",
      -  "city-wide",
      -  "desk-wide",
      -  "neon-wide",
      -  "studio-wide"
      -]New value: +[
      +  "closeup",
      +  "closeup-wide",
      +  "outdoors",
      +  "bookshelf",
      +  "two-hands",
      +  "on-desk",
      +  "dim-room",
      +  "city-wide",
      +  "desk-wide",
      +  "neon-wide",
      +  "studio-wide"
      +]
    • changedInput schema / properties / videoFormat / description
      Previous value: -"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."New value: +"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. \"16:9\" (widescreen) is for the notification tools with background.backgroundType \"floating\" only, where the frame is a photo scene and any aspect ratio applies without a bezel; on any other clip it is ignored. Default: the iPhone bezel, 9:16."
    • changedInput schema / properties / videoFormat / enum
      Previous value: -[
      -  "9:16",
      -  "9:19.5",
      -  "3:2",
      -  "1:1"
      -]New value: +[
      +  "9:16",
      +  "9:19.5",
      +  "3:2",
      +  "1:1",
      +  "16:9"
      +]
  3. Changed1 schema field changed
    • addedInput schema / properties / intro / properties / selfAvatarUrl
      Added value: +{
      +  "format": "uri",
      +  "maxLength": 2000,
      +  "type": "string"
      +}
  4. 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"
      +}
  5. 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"
      +}
  6. 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"
      +}
  7. 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"
      +}
  8. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only say it creates something non-destructively; the description adds the behavior that actually matters: a MockClip watermark and 2-render cap on the free plan, a returned link that prompts the user to attach each `upload:` image before export, and the rule never to ask the user to host an image. That is substantial disclosure beyond the annotation set.

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?

Purpose is front-loaded and every clause is technically informative, but it is delivered as one long paragraph of nested parentheticals (the opening feature list, the flow-screen enumeration, the image-upload digression). It would be far more usable split into purpose / options / images / plan-limits sections.

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

Completeness4/5

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

For a 33-parameter, deeply nested, no-output-schema render tool, the description covers the core workflow, the tricky enums, and the plan/watermark consequences, and it hints at the returned link. Gaps remain around the many secondary screen objects and timing parameters, but nothing an agent must know to invoke it correctly is missing.

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 27% schema coverage across 33 parameters, the description carries most of the load and does so for the hard ones: flow transitions, keyboard auto/always/never, showTaps default, the dateLabel → timestamp → TODAY fallback with firstDateLine, `hasStory: false`, `group.members` naming rules, and the `upload:<label>` image convention with a same-label/different-label rule. Many remaining parameters (theme, intro, soundSettings, contactStatus, camera/videoCall media, gifs) are left to name inference and their schema entries.

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?

Opens with a specific verb+resource ("Create a Messenger conversation animation") and enumerates Messenger-specific artifacts (sent/read check marks, three-dot typing bubble, avatar-as-read-mark) that separate it from the iMessage/WhatsApp/Discord siblings. It never names an alternative tool or states when to pick Messenger over them, so it falls short of a 5.

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 real conditional guidance: pass `flow`/`chatList`/per-screen objects to walk the app, otherwise "the clip shows the conversation only"; `story` steps need `params: { story: n }`; group chats need at least three different authors; free-plan callers should be told about /pricing. No exclusions or sibling routing are stated, keeping it at 4.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources