Skip to main content
Glama

iMessage notifications video

create_imessage_notification

Create an iMessage notification (banner) animation. Banners come one at a time; with stackNotifications: true they pile up instead, as on the lock screen — the newest on top pushing the earlier ones down, up to 4 on screen (a 5th makes the oldest leave). background.backgroundType "floating" swaps the phone screen for a photo of a phone lying on a table: the notification pops out of it as a glass pill and is mirrored on its screen (one at a time, no bezel; floatingScene.plate picks the photo, floatingScene.align "center" centres the pill over the phone and "right" lines its right end up with the phone's right edge (default: over the phone's far edge), frame videoFormat "16:9" the wide frame). 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": {
      "notifications": "<notifications>"
    },
    "name": "create_imessage_notification"
  }
}

Input Schema

NameRequiredDescriptionDefault
themeNo
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.
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.
backgroundNo
lockScreenNo
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.
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.
floatingSceneNo
notificationsYes
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.
showHomeIndicatorNoDraw the iOS home indicator bar at the bottom of the screen (default true).
backgroundImageUrlNo
stackNotificationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / floatingScene / properties / align
      Added value: +{
      +  "enum": [
      +    "default",
      +    "center",
      +    "right"
      +  ],
      +  "type": "string"
      +}
    • 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. Changed6 schema fields changed
    • changedInput schema / properties / background / properties / backgroundType / enum
      Previous value: -[
      -  "default",
      -  "chroma",
      -  "image",
      -  "transparent",
      -  "lockscreen"
      -]New value: +[
      +  "default",
      +  "chroma",
      +  "image",
      +  "transparent",
      +  "lockscreen",
      +  "floating"
      +]
    • addedInput schema / properties / floatingScene
      Added value: +{
      +  "properties": {
      +    "imageUrl": {
      +      "format": "uri",
      +      "maxLength": 2000,
      +      "type": "string"
      +    },
      +    "plate": {
      +      "enum": [
      +        "daylight-desk",
      +        "evening-desk"
      +      ],
      +      "type": "string"
      +    },
      +    "screenQuad": {
      +      "items": {
      +        "maximum": 1,
      +        "minimum": 0,
      +        "type": "number"
      +      },
      +      "maxItems": 8,
      +      "minItems": 8,
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
    • 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 / stackNotifications
      Added value: +{
      +  "type": "boolean"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / background / properties / chromaStyle
      Added value: +{
      +  "enum": [
      +    "original",
      +    "keysafe"
      +  ],
      +  "type": "string"
      +}
  5. Changed1 schema field changed
    • removedInput schema / properties / background / properties / chromaStyle
      Removed value: -{
      -  "enum": [
      -    "original",
      -    "keysafe"
      -  ],
      -  "type": "string"
      -}
  6. Changed1 schema field changed
    • addedInput schema / properties / background / properties / chromaStyle
      Added value: +{
      +  "enum": [
      +    "original",
      +    "keysafe"
      +  ],
      +  "type": "string"
      +}
  7. 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"
      +}
  8. 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"
      +}
  9. 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"
      +}
  10. 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 is a non-idempotent, non-destructive write, so the description carries the real burden and does so: stacking caps at 4 on screen with the 5th evicting the oldest, floating mode renders a glass pill mirrored on a photo, free-plan exports carry a MockClip watermark and only 2 MCP renders, and the returned link prompts the user to add each `upload:` image from their device. That is material behavior an agent could not 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.

Conciseness3/5

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

The purpose is front-loaded and every sentence carries information, but the middle floating-background sentence is a run-on with stacked parentheticals ('(one at a time, no bezel; `floatingScene.plate` picks the photo, ...') that is genuinely hard to parse. The free-plan note at the end is useful but reads as an appended afterthought rather than organized content.

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 17-parameter nested-object tool with no output schema, the description covers the non-obvious behaviors an agent would otherwise get wrong — stacking overflow, floating scene composition, transparency/export interaction, watermark and render limits, and the upload handoff. It leaves a fair number of secondary parameters to the schema, which is acceptable but not fully complete.

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?

At 53% schema coverage across 17 parameters, the description usefully compensates for the highest-risk ones: stackNotifications semantics and overflow, background.backgroundType 'floating' plus floatingScene.plate/align and the 16:9 frame interaction, and the `upload:<label>` convention that applies to every image field with the rule to reuse labels per image. Many other parameters (theme, lockScreen fields, soundSettings, per-notification delayBefore/displayDuration/dismissStyle) get no treatment and are left to 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 opening sentence gives a specific verb and resource: 'Create an iMessage notification (banner) animation.' That is clearly distinct from a conversation-thread tool in substance, but the description never names the nearby alternative (create_imessage_conversation) or states the boundary, so the agent must infer the split itself.

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?

It conditions usage well in specific places: stackNotifications:true 'when they pile up as on the lock screen', floating background 'swaps the phone screen for a photo of a phone lying on a table', textScale used when a single notification should fill the screen. The image guidance is explicit ('Never ask the user to host an image somewhere'; use `upload:<label>` for chat-attached images). It stops short of naming when to choose this tool over its siblings.

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