Skip to main content
Glama
Sign In

Agency Autopilot

by com.jiyumarketing.mcp
OverviewDiscussionsAdmin

Google Ads: Create demand gen ad

ads_create_demand_gen_ad

Add an image or video ad to an existing Demand Gen ad group. Created paused. The preview sends the exact request to Google to check and creates nothing; show the ad to the person verbatim before confirming. Videos must already be on YouTube.

Input Schema

NameRequiredDescriptionDefault
formatYesimages: a multi-image ad (photos and a logo). video: a video ad from YouTube videos already uploaded to YouTube.
confirmNoLeave false to preview: nothing changes and the preview shows exactly what would happen. Set true only after the user has agreed to this exact change.
logo_urlYesSquare logo, JPG/PNG/GIF, at least 128x128
final_urlYesThe page this ad sends people to
headlinesYes1-5 short headlines
image_urlsNoImages ads only: public JPG/PNG/GIF URLs, sorted into slots by shape: landscape 1.91:1 (min 600x314), square 1:1 (min 300x300), portrait 4:5 (min 480x600), tall 9:16 (min 600x1067). At least one landscape or square.
ad_group_idYesA Demand Gen ad group, from ads_report
customer_idYes
descriptionsYes1-5 descriptions, max 90 characters each
business_nameYesThe advertiser's name as it shows on the ad, max 25 characters
call_to_actionNoImages ads only: button text such as 'Get quote'. Google picks one when left out.
long_headlinesNoVideo ads only: 1-5 long headlines
youtube_videosNoVideo ads only: 1-5 YouTube links or video ids. The video must already be on YouTube (public or unlisted); videos can't be uploaded here.
acknowledge_landingNoOnly after the preview's landing_check warned AND the person has seen the warnings and still wants this page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

The description adds important behavior beyond annotations: ads are created paused, preview sends the exact request but creates nothing, the ad should be shown verbatim before confirming, and videos cannot be uploaded here. These are critical operational details for a mutating open-world tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and compact: purpose first, then creation status, preview workflow, and the YouTube constraint. Every sentence adds useful information without repetition.

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 14-parameter mutation with no output schema, the description covers the essential behavioral context: preview safety, paused creation, and video prerequisites. Parameter details are handled well by the schema, though it does not mention the landing-check acknowledgment flow that appears in the schema.

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 93%, so the schema already carries nearly all parameter meaning. The description reinforces the image/video distinction and YouTube prerequisite, but adds little parameter-level detail beyond what is already documented.

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?

The description uses a specific verb and resource: adding an image or video ad to an existing Demand Gen ad group. This distinguishes it from generic ad creation and campaign creation siblings without requiring schema inspection.

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 clearly states the tool adds to an existing ad group, describes the preview-confirm workflow, and gives the prerequisite that videos must already be on YouTube. It does not explicitly name the alternative sibling for non-Demand Gen ads, but the scope is clear from the purpose statement.

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

All Agency Autopilot 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