Skip to main content
Glama
Sign In

PPC Ad Editor

by com.ppcadeditor
OverviewDiscussionsAdmin

Preview an ad

preview_ad
Read-only

Show a realistic mockup of one ad (Google Search, Display, Performance Max, Demand Gen, YouTube, Facebook/Instagram, LinkedIn) right in the chat. No account needed. The ad copy comes from the caller. Images are hosted HTTPS URLs in images[] / logos[], for example from the advertiser's website; this tool never generates images, and Google Search ads need none. Studio, YouTube and www.ppcadeditor.com images load directly. Any other HTTPS image is shown through a signed URL on studio.ppcadeditor.com. One format per call. The result includes save_url, a link where the user can save the ad to a free PPC Ad Editor account, edit it, and get a share link for a client.

Format specs (items allowed per field, max characters per item):

  • RSA (Google Search): headlines 3-15 (max 30 chars), descriptions 2-4 (max 90 chars)

  • RDA (Google Display): headlines 1-5 (max 30 chars), long_headlines 0-1 (max 90 chars), descriptions 1-5 (max 90 chars)

  • PMAX (Performance Max): headlines 1-15 (max 30 chars), long_headlines 0-5 (max 90 chars), descriptions 1-5 (max 90 chars)

  • DEMAND_GEN (Google Demand Gen): headlines 1-5 (max 40 chars), long_headlines 0-5 (max 90 chars), descriptions 1-5 (max 90 chars)

  • META_SINGLE (Facebook/Instagram single): headlines 1-5 (max 40 chars), descriptions 0-5 (max 25 chars), primary_texts 0-5 (max 125 chars)

  • META_CAROUSEL (Facebook/Instagram carousel): headlines 1-10 (max 40 chars), descriptions 0-10 (max 25 chars), primary_texts 0-5 (max 125 chars)

  • META_STORY (Facebook/Instagram story): primary_texts 0-5 (max 125 chars)

  • LINKEDIN_SINGLE (LinkedIn single): headlines 1 (max 200 chars), descriptions 1 (max 300 chars), primary_texts 0-1 (max 600 chars)

  • LINKEDIN_CAROUSEL (LinkedIn carousel): headlines 1-10 (max 45 chars), descriptions 1-10 (max 70 chars), primary_texts 0-1 (max 600 chars)

  • YOUTUBE (YouTube): headlines 1-5 (max 30 chars), long_headlines 0-1 (max 90 chars), descriptions 1-5 (max 90 chars)

Input Schema

NameRequiredDescriptionDefault
nameNoOptional name for the ad, used if the user saves it
logosNoCore ad-body logos (brand/profile image shown next to the ad on Meta, LinkedIn, RDA, PMAX).
formatYesAd format of the mockup. Field limits per format are listed in the format specs.
imagesNoCore ad-body images (Meta hero, Carousel cards, PMAX assets, etc.). Feature-gated per format. Google image EXTENSIONS (shown below an RSA text ad) go in extensions.images.
videosNoCore ad-body videos (YouTube URLs). Primary for YOUTUBE format, optional for Meta/PMAX/RDA.
final_urlYes
headlinesNoShort headlines. The character limit depends on the format and is listed in this tool's format specs. Google Search headlines are 30 characters. There is no single limit for every format.
extensionsNoAd extensions (aka ad assets). Google formats only — ignored on Meta/LinkedIn/YouTube.
descriptionsNoNot the Facebook or Instagram body. On META_SINGLE and META_CAROUSEL this is the optional link line under the headline, 25 characters, and it may be omitted. Body copy belongs in primary_texts (125 characters). Google Search descriptions are required and 90 characters. Other formats are in the format specs.
business_nameNoBusiness name shown on the ad. 25 characters.
primary_textsNoBody copy for Facebook, Instagram and LinkedIn. META_SINGLE, META_CAROUSEL and META_STORY: 125 characters. Google Search does not use this field.
call_to_actionNoButton label, for example Learn more. 30 characters.
display_path_1NoOptional Google display path. 15 characters.
display_path_2NoOptional second Google display path. 15 characters.
long_headlinesNoLong headlines for Performance Max, Display and Demand Gen. Character limits are in the format specs. Google Search and Meta do not use this field.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedInput schema / properties / business_name / description
      Added value: +"Business name shown on the ad. 25 characters."
    • addedInput schema / properties / call_to_action / description
      Added value: +"Button label, for example Learn more. 30 characters."
    • addedInput schema / properties / call_to_action / maxLength
      Added value: +30
    • addedInput schema / properties / descriptions / description
      Added value: +"Not the Facebook or Instagram body. On META_SINGLE and META_CAROUSEL this is the optional link line under the headline, 25 characters, and it may be omitted. Body copy belongs in primary_texts (125 characters). Google Search descriptions are required and 90 characters. Other formats are in the format specs."
    • addedInput schema / properties / display_path_1 / description
      Added value: +"Optional Google display path. 15 characters."
    • addedInput schema / properties / display_path_1 / maxLength
      Added value: +15
    • addedInput schema / properties / display_path_2 / description
      Added value: +"Optional second Google display path. 15 characters."
    • addedInput schema / properties / display_path_2 / maxLength
      Added value: +15
    • addedInput schema / properties / headlines / description
      Added value: +"Short headlines. The character limit depends on the format and is listed in this tool's format specs. Google Search headlines are 30 characters. There is no single limit for every format."
    • addedInput schema / properties / long_headlines / description
      Added value: +"Long headlines for Performance Max, Display and Demand Gen. Character limits are in the format specs. Google Search and Meta do not use this field."
    • addedInput schema / properties / primary_texts / description
      Added value: +"Body copy for Facebook, Instagram and LinkedIn. META_SINGLE, META_CAROUSEL and META_STORY: 125 characters. Google Search does not use this field."
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the read-only and non-destructive annotations, the description discloses that it does not generate images, requires hosted HTTPS image URLs, explains how external images are routed through signed URLs, and notes that the result includes save_url. These are meaningful behavioral details for an agent to understand before calling.

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 purpose and then organized into useful format specs. It is long, but the length is largely justified by 10 formats and 15 parameters; some operational details could be tightened.

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?

The definition is largely complete for invoking the tool: it covers image constraints, one-format-per-call behavior, and save_url. With no output schema, it could more fully describe the return shape beyond save_url, but the invocation-critical context is present.

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

Parameters5/5

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

Although schema description coverage is already high at 93%, the description adds substantial meaning by listing per-format field allowances and character limits. It also clarifies field distinctions such as Google Search not using primary_texts and extensions being ignored on non-Google formats.

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 uses a specific verb and resource: 'Show a realistic mockup of one ad' and lists the supported ad formats. It clearly distinguishes previewing from generating images, but it does not explicitly differentiate itself from the sibling get_ad_formats tool.

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?

It gives useful context such as 'No account needed,' 'One format per call,' and that ad copy comes from the caller. However, it does not explicitly say when to use this tool versus get_ad_formats or when not to use it.

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

All PPC Ad Editor 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