Skip to main content
Glama

Prepare a product video ad

create_ad

Prepares video ads for a product, one per format (vertical 9:16 for Reels and TikTok, square 1:1, wide 16:9), from the product's page (Shopify, Amazon, Etsy or any shop) or its name. Returns the link to Cirrela's product-ad page filled in: the page reads the product when the person taps Import, shows the start images and the cost before anything is spent. This tool fetches nothing and renders nothing. Fits "make an ad for my product", "fais une pub vidéo pour mon produit", "haz un anuncio en vídeo de mi producto", "faça um anúncio em vídeo do meu produto".

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

Input Schema

NameRequiredDescriptionDefault
productNoOr, without a page: the product in a few words.
languageNoOptional: the page's language, usually the one the person writes in. Default en.
product_urlNoThe product's page, https://…

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses behavior an agent could not otherwise know: the tool returns a link to a pre-filled page, the product import happens only on the user's tap, and cost is shown before anything is spent. The "fetches nothing and renders nothing" line sets expectations against the render-oriented siblings, which is high-value behavioral context.

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?

Core capability and the crucial "nothing is rendered or spent" constraint are front-loaded, and the multilingual trigger phrases serve a concrete routing purpose. The utterance list is somewhat long relative to the rest, but no sentence is pure filler.

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

Completeness5/5

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

There is no output schema, yet the description fully explains the return value and the downstream flow (page imported by the user, images and cost shown before spend). For a three-parameter, zero-required preparation tool, nothing an agent needs in order 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 description coverage is 100%, so the schema already documents that product_url and product are alternative input modes. The description echoes this with "from the product's page … or its name" and mentions supported shops, but adds no format, validation, or precedence rules, and says nothing about the language parameter. Baseline 3 is appropriate.

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 gives a specific verb and resource ("Prepares video ads for a product") plus the exact output set: one ad per format, with the aspect ratios named. It also separates itself from rendering siblings by stating "This tool fetches nothing and renders nothing," though it never names create_video or create_film directly.

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 gives clear triggering context via example utterances in four languages ("make an ad for my product", "fais une pub vidéo…"), which tells an agent exactly what user intent maps here. It stops short of naming an alternative tool or stating when-not to call it, so it lands at 4 rather than 5.

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