Skip to main content
Glama

Notification Popup Animation Maker

create_notification_popup_animation
Read-onlyIdempotent

Prefill the Notification Popup Animation Maker: a phone-style notification that slides in, holds and slides out, with your own title and message. Returns a link that opens the Tool with these options; the user presses Export there to download the video. All options are optional. Icons and images that need a file upload are not supported.

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

Input Schema

NameRequiredDescriptionDefault
bgNoBackground color. Default: "#00ff00".
appNoApp name shown in the notification header. Default: "Messages".
fpsNoExport frame rate. Default: "30".
msgNoNotification message line. Default: "Hey! Are we still on for tonight?".
resNoExport resolution. Default: "720".
fontNoFont id of the text. Default: "inter".
holdNoSeconds the notification stays on screen. Default: 3.
iconNoIcon tile: one emoji or letter, or a library id such as "symbol:bell" or "brand:whatsapp". Uploaded images are not supported. Default: "symbol:message-square".
leadNoSeconds of empty frame before the notification slides in. Default: 0.5.
lookNoLight or dark notification style. Default: "light".
sizeNoVideo size (aspect ratio) preset. Default: "16:9".
tailNoSeconds of empty frame after the notification leaves. Default: 0.5.
timeNoTime label shown in the notification, such as "now". Default: "now".
scaleNoSize of the notification relative to the frame. Default: 100.
titleNoNotification title line. Default: "New message".
accentNoAccent color of the icon tile. Default: "#2563eb".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so safety is covered; the description adds genuinely new behavior by clarifying that the output is a prefill link rather than a video and that export is a separate user action. It does not address link lifetime, permissions, or whether existing state is affected.

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?

Four short sentences, front-loaded with what the tool produces and followed by the return-value caveat and the upload limitation. "All options are optional" is slightly redundant given zero required parameters but is not harmful.

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?

Given 16 optional parameters and no output schema, the description does what it must: explains what comes back (a link) and what the user must do next (press Export). It could say more about link persistence or failure modes, but nothing needed to call it correctly is missing.

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

Parameters3/5

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

Schema coverage is 100% with defaults and enums documented for all 16 parameters, so the schema carries the semantics. The description's only parameter-relevant additions – title/message customizability, all-optional, and no uploaded icon files – largely restate what the schema already says.

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 – "Prefill the Notification Popup Animation Maker" – and follows with a concrete description of the artifact (a phone-style notification that slides in, holds, and slides out). The animation type named distinguishes it from the sibling animation creators without requiring the schema.

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?

Explains the actual workflow: this tool returns a link that opens the Tool, where the user must press Export to download the video — essential for an agent that might otherwise expect a rendered file. It also states an explicit exclusion (file-upload icons/images unsupported) and that all options are optional, but gives no guidance on when to prefer this over other animation tools.

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.