Skip to main content
Glama

VidGuy

by ai.vidguy
OverviewDiscussionsAdmin

Generate ads from a store, product, service or app URL

generate_ads_from_url
Destructive

Ads on demand: give the URL of an online store, a single product page, a service business's site, or an App Store / Google Play listing, and get paid-social ads made from the REAL products, prices, reviews and offers on that page (claims are verified against the page; nothing is invented). No brand setup needed. Pro and Scale plans. SPENDS CREDITS: 3 for reading the site + static-ad 8 each (returns 2 A/B variants), ugc-ad 25, greenscreen-ad 25, animated-ad 60, music-ad 70 (+3 with render). Defaults: a store gets 3 static-ad + 1 ugc-ad (52 credits, 7 ads); a service business or app gets ugc-ad + animated-ad (88 credits). Types: static-ad (2 finished image ads for the same product in different formats, e.g. review card + benefit callouts, for A/B testing; stores only), ugc-ad (9:16 presenter talking to camera, ~15s), greenscreen-ad (presenter reacting over a scrolling screenshot of the page), animated-ad (~30s narrated claymation / Pixar-style / felt / cartoon story ad), music-ad (~30s animated music video: a character sings an original song about a relatable moment, the product revealed in the last chorus; the agent picks the genre and look unless prompt asks for one). ASYNC: reading the site takes 15-30s before the jobId returns; generation then takes ~1-3 minutes. Poll get_job. Pass render=true for viewable PNG/MP4 files. Use prompt to steer every ad (theme, audience, angle, and for music-ad the genre or animation look). Credits refund automatically on failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesStore home page, product page, service business site, or App Store / Google Play listing. Bare domains work.
nameNo
countNoTotal ads (1-5); repeats the requested types.
typesNoAd types to make (omit for the default pack).
promptNoFree-form creative steer applied to every ad, e.g. 'Halloween theme' or 'target new parents'.
renderNoAlso render PNG/MP4 files server-side (+3 credits).
languageNoLanguage to write the ads in: on-screen text, script and voice-over (ISO 639-1, e.g. 'es', 'de', 'fr'). Defaults to English. The store's facts and reviews are translated when its page is in another language; brand and product names, prices and discount codes stay as on the page.
adFormatsNoPin the static-ad layouts in order; formats without supporting data are skipped.
adAspectRatioNoFrame for static-ad (default 4:5). Video ads are always 9:16.
animationStyleNoLook for animated-ad (else chosen per brand).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobIdYes
sourceNo
statusYes
pollUrlYes
creditsReservedYes
snackTypeSequenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / language / description
      Previous value: -"ISO 639-1 language override (defaults to the page's language)."New value: +"Language to write the ads in: on-screen text, script and voice-over (ISO 639-1, e.g. 'es', 'de', 'fr'). Defaults to English. The store's facts and reviews are translated when its page is in another language; brand and product names, prices and discount codes stay as on the page."
    • addedInput schema / properties / language / enum
      Added value: +[
+  "en",
+  "es",
+  "fr",
+  "de",
+  "it",
+  "pt",
+  "nl",
+  "pl",
+  "sq",
+  "tr",
+  "ru",
+  "ar",
+  "hi",
+  "id",
+  "vi",
+  "th",
+  "ja",
+  "ko",
+  "zh"
+]
    • removedInput schema / properties / language / maxLength
      Removed value: -5
    • removedInput schema / properties / language / minLength
      Removed value: -2
    • changedInput schema / properties / types / items / enum
      Previous value: -[
-  "static-ad",
-  "ugc-ad",
-  "animated-ad",
-  "greenscreen-ad"
-]New value: +[
+  "static-ad",
+  "ugc-ad",
+  "animated-ad",
+  "greenscreen-ad",
+  "music-ad"
+]
    • changedInput schema / properties / types / maxItems
      Previous value: -4New value: +5
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing per-type credit costs, default packs, async timing (15-30s site read, 1-3 min generation, poll get_job), render cost, and automatic refund on failure. This is exactly the mutation/cost behavior an agent needs, and it does not contradict destructiveHint/openWorldHint.

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?

Front-loaded with purpose and cost, then defaults, then type definitions. Dense but nearly every clause carries actionable detail. Slightly long as one block; the type definitions could be tightened, but little 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?

With an output schema present, the description needn't explain return values, and annotations cover safety. Combined with full cost, async, default, and workflow guidance, an agent has everything needed to invoke and poll correctly.

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?

Schema coverage is 90%, so baseline is 3, but the description adds real meaning: it explains what each ad type produces, how count repeats types, that render yields viewable PNG/MP4, and how prompt steers every ad including music-ad genre. Enum-driven params (adFormats, adAspectRatio, animationStyle) are left to the schema, so it is not a full 5.

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+resource (generate paid-social ads from a URL) and enumerates accepted sources (store, product page, service site, App Store / Google Play listing). This clearly distinguishes it from sibling generation tools like create_video, studio_generate_video, or generate_meme.

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?

Gives strong when-to-use context: 'No brand setup needed', Pro and Scale plan requirement, and explicit defaults per source type (store gets 3 static + 1 ugc; service/app gets ugc + animated). It stops short of naming sibling alternatives to use instead for non-ad video needs, so it is clear context rather than full when/when-not routing.

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

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