Skip to main content
Glama

google_ads_callouts_create

Create a callout asset and attach it to a Google Ads campaign, respecting the 20-callout limit per campaign. Returns the new asset's resource name or an error if limit reached.

Instructions

Create a callout Asset and link it to a Google Ads campaign in a two-step mutate (AssetService then CampaignAssetService). Returns {resource_name} of the newly created asset, or {error:true, error_type:'validation_error', message} when the campaign already has 20 callouts (_MAX_CALLOUTS_PER_CAMPAIGN limit). Mutating — reversible only by google_ads_callouts_remove. The asset is minted per call, so identical text creates duplicate asset rows. For sitelink variants use google_ads_sitelinks_create.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idNoGoogle Ads customer ID as a 10-digit string without dashes (e.g. '1234567890'). Optional — falls back to GOOGLE_ADS_CUSTOMER_ID / GOOGLE_ADS_LOGIN_CUSTOMER_ID from the configured credentials when omitted.
campaign_idYesCampaign ID as a numeric string without dashes (e.g. '23743184133'). Obtain via google_ads_campaigns_list.
callout_textYesCallout text shown below the ad (e.g. 'Free shipping', '24/7 support'). Google Ads limit: 25 characters.
Behavior5/5

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

With no annotations, the description fully discloses mutation, reversibility by remove tool, duplication behavior, error on limit, and the two-step service call. Leaves no behavioral gaps.

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?

Four dense sentences front‑loading the purpose. No wasted words; every sentence adds crucial information.

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?

Despite no output schema, description specifies return shape ({resource_name} or error). Parameters are fully covered, and sibling tools are named. Complete for a creation tool in this context.

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 has 100% coverage; description adds context: customer_id fallback, campaign_id source, callout_text maxLength and examples. Adds meaningful value beyond 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?

Clearly describes creating a callout asset and linking it to a campaign via a two-step mutate. Distinguishes from google_ads_sitelinks_create. Mentions return values and error conditions.

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

Usage Guidelines5/5

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

Explicitly notes when to use (create callout), when not (campaign limit of 20), and alternative tool for sitelinks. Also warns about duplicate creation from identical text.

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/logly/mureo'

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