Skip to main content
Glama

Create Ad Creative

create_ad_creative
Destructive

Create an ad creative (image, video, carousel, or text ad).

The Creative Asset agent can help generate ad visuals and copy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesAd body text
nameNoCreative name
adSetIdNoAd set ID (optional)
headlineYesAd headline
mediaUrlsNoMedia URLs for the creative
campaignIdYesCampaign ID
landingUrlNoLanding page URL
callToActionNoCall to action button text
creativeTypeYesCreative type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

The description does not disclose any behavioral traits beyond what annotations already indicate (e.g., destructiveHint=true). It fails to explain side effects, permissions, or what happens when an ad creative is created.

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 concise and front-loaded with purpose. The second sentence about the Creative Asset agent is somewhat tangential but not overly verbose.

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 and no output schema, this description is inadequate. It does not explain return values, how creative types map to required fields, or how the creative integrates with the campaign.

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 baseline is 3. The description only repeats creativeType enum values without adding extra meaning to the parameters.

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 clearly states the tool creates an ad creative and lists supported types (image, video, carousel, text). It is distinct from sibling tools like create_ad_campaign by resource, though it does not explicitly contrast them.

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?

There is no guidance on when to use this tool versus alternatives. The mention of the Creative Asset agent is a general suggestion for help, not a conditional usage instruction.

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.