Skip to main content
Glama
Sign In

PopNow

by io.github.popnow-ai
OverviewDiscussionsAdmin

Apply a video effect

apply_effect

Turn a photo into a fun effect video, like Zombie Turn, Flying Car, Tiny Planet or Molten Gold, or a quick photo makeover like Clay Figure or Pixel Art. Videos take 1 to 3 minutes. Uses site credits with OAuth or USD with an API key; the tool quotes the price.

Input Schema

NameRequiredDescriptionDefault
imageNoChatGPT only: the photo the user attached. Use image_url everywhere else.
effectYesWhich effect, by name or id. Popular: Zombie Turn, Flying Car, Tiny Planet, Molten Gold, Hyperdrive, Werewolf Turn, Costume Spin, Groove Dance. Call list_models with category effects to see all of them.
max_usdNoAPI key only: maximum approved USD as a decimal string with up to 9 fractional digits. Set currency to USD. Only set after the user confirms the quoted cost_usd. Never convert max_credits.
currencyNoBilling unit: USD for API keys; credits for OAuth (optional for existing OAuth clients).
image_urlNoThe photo to animate: a public https link, or a popnow:// link from an earlier result. A clear photo of one person works best.
max_creditsNoOAuth only: the most site credits the user agreed to spend on this. Only set it after the user confirmed a quoted price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / currency
      Added value: +{
+  "description": "Billing unit: USD for API keys; credits for OAuth (optional for existing OAuth clients).",
+  "type": "string"
+}
    • changedInput schema / properties / image / type
      Previous value: -[
-  "null",
-  "object"
-]New value: +"object"
    • changedInput schema / properties / max_credits / description
      Previous value: -"The most credits the user agreed to spend on this. Only set it after the user confirmed a quoted price."New value: +"OAuth only: the most site credits the user agreed to spend on this. Only set it after the user confirmed a quoted price."
    • addedInput schema / properties / max_usd
      Added value: +{
+  "description": "API key only: maximum approved USD as a decimal string with up to 9 fractional digits. Set currency to USD. Only set after the user confirms the quoted cost_usd. Never convert max_credits.",
+  "type": "string"
+}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent, open-world mutation. The description adds valuable behavioral context beyond annotations: videos take 1–3 minutes, billing differs between OAuth credits and API-key USD, and the tool quotes the price before spending. It does not cover return values, but that is acceptable without an output schema.

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?

The description is front-loaded with the core action and examples, then adds timing and billing information. It is appropriately sized and readable, though the example list could be trimmed slightly without losing meaning.

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 mutation tool with full schema coverage and annotations, the description provides the key missing context: latency and payment/quotation behavior. It does not explain return payloads, but no output schema exists, and the core calling information is present.

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 description coverage is 100%, so parameter meaning is already well documented. The description adds only billing context and a mention that the tool quotes price, without expanding on parameter constraints beyond what the schema already says.

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 clearly states a specific verb and resource: turning a photo into an effect video or photo makeover, with named examples. It does not explicitly differentiate the tool from siblings like create_video or edit_image, but the effect-focused phrasing makes its niche understandable.

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?

The description gives use-case examples but no explicit guidance on when to choose apply_effect over alternatives such as edit_image or create_video. Usage is implied by 'fun effect video' and 'photo makeover,' but there is no when-not or alternative-routing instruction.

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

All PopNow 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