Skip to main content
Glama

MockClip

by com.mockclip
OverviewDiscussionsAdmin

Shopify notifications video

create_shopify_notification

Create a Shopify notification animation: each notifications entry is one banner (title in bold beside the time — default "now" — and the body wrapped under them, up to 4 lines) that slides in after delayBefore seconds (default 0.5), stays displayDuration seconds (default 4) and leaves by sliding up or fading (dismissStyle); 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), with the Shopify app icon. background.backgroundType: default (theme colour), chroma (chromaColor; chromaStyle "original" — the default, with fades and shadow — or "keysafe" for one-threshold keyers like Clipchamp), image (backgroundImageUrl), transparent (alpha in MOV / WebM) or lockscreen (wallpaper, date and clock: lockScreen). 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

NameRequiredDescriptionDefault
themeNo
sceneIdNoComposite 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.
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. 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.
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
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. Changed1 schema field changed
    • addedInput schema / properties / stackNotifications
      Added value: +{
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / background / properties / chromaStyle
      Added value: +{
+  "enum": [
+    "original",
+    "keysafe"
+  ],
+  "type": "string"
+}
  3. Changed1 schema field changed
    • removedInput schema / properties / background / properties / chromaStyle
      Removed value: -{
-  "enum": [
-    "original",
-    "keysafe"
-  ],
-  "type": "string"
-}
  4. Changed1 schema field changed
    • addedInput schema / properties / background / properties / chromaStyle
      Added value: +{
+  "enum": [
+    "original",
+    "keysafe"
+  ],
+  "type": "string"
+}
  5. 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"
+}
  6. 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"
+}
  7. 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"
+}
  8. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint false, destructiveHint false), the description discloses substantive behavior: per-banner timing defaults, one-at-a-time vs stacked playback with a 4-on-screen cap and 5th-evicts-oldest rule, background type semantics, and the free-plan watermark plus the 2-render MCP limit. That is exactly the extra context annotations cannot carry.

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 core concept is front-loaded, but the remainder is one dense run-on paragraph mixing banner timing, stacking, background modes and plan/watermark policy. Every sentence carries information, yet the lack of structure (no separation of options vs billing caveats) makes it harder to scan than it needs to be.

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 15-parameter nested tool with no output schema, the description covers the required array plus the most consequential options and the plan gating that affects exports. Minor gaps (theme, soundSettings, showHomeIndicator, textScale) are partly covered by schema descriptions and are low-risk defaults, so the definition is nearly complete.

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

Parameters5/5

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

With 53% schema coverage, the description compensates well: it explains the notifications array fields (title bold, time default "now", 4-line body wrap, delayBefore 0.5, displayDuration 4, dismissStyle), stackNotifications behavior, and the background.backgroundType branches including chromaStyle and backgroundImageUrl. These add meaning well beyond the bare schema, even though theme and soundSettings are not 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 description opens with a specific verb+resource ("Create a Shopify notification animation") and immediately explains the core payload, so the agent knows this produces a branded notification-banner video. It does not explicitly contrast itself with the near-identical sibling create_brand_free_notifications, relying on the Shopify branding to differentiate.

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 detailed option walkthrough (single vs stacked banners, background types), and there is a plan-related instruction (mention upgrade at /pricing on free plan). But there is no explicit "use this when / instead of X" guidance against the many sibling notification/chat tools, so selection still requires inference.

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

All MockClip toolsInspect
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