Skip to main content
Glama

create_display_campaign

Destructive

Create a Google Ads Display campaign with responsive ads and image uploads from URLs to reach audiences across websites and apps.

Instructions

Create a Google Ads Display campaign with responsive display ads. Supports image uploads from URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
final_urlYesLanding page URL
headlinesYesHeadlines (1-5, max 30 chars each)
geo_targetsNoGeo target codes
daily_budgetYesDaily budget in USD
descriptionsYesDescriptions (1-5, max 90 chars each)
business_nameYesBusiness name (max 25 chars)
campaign_nameYesName for the campaign
square_image_urlNoURL to 1200x1200 square image
landscape_image_urlNoURL to 1200x628 landscape image
Behavior2/5

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

The annotations include destructiveHint: true, indicating this tool modifies resources. The description only adds 'Create' and 'Supports image uploads from URLs', which aligns with the annotation but does not provide additional behavioral context such as costs, permissions, or side effects.

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 a single sentence that is concise and front-loaded with the core purpose. There is no unnecessary information.

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

Completeness2/5

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

For a tool with 9 parameters, 6 required, and no output schema, the description is too brief. It does not explain return values, campaign lifecycle, or provide operational context critical for correct usage.

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 parameters. The description adds marginal value by linking 'image uploads from URLs' to the image URL parameters, but overall it does not significantly enhance understanding beyond the schema.

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 clearly states 'Create a Google Ads Display campaign with responsive display ads', specifying the verb and resource. It distinguishes from sibling tools like create_search_campaign by explicitly mentioning 'Display' and 'responsive display ads'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide guidance on when to use this tool versus alternatives. It mentions 'Supports image uploads from URLs' but does not contrast with other campaign creation tools or specify scenarios where this tool is preferred.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jshorwitz/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server