AdCopilot

Google Ads: create callout asset

create_callout_asset

Creates a callout asset that can be linked to campaigns or ad groups.

Creating it changes no ad: it shows only once linked with
link_asset_to_campaign, link_asset_to_ad_group or
link_assets_to_customer.

Callouts add short snippets of text to your ad (e.g., "Free Shipping", "24/7 Support").

Args:
    customer_id: The Google Ads customer ID (numbers only, no hyphens).
    callout_text: The callout text (max 25 characters).
    start_date: Start date in YYYY-MM-DD format. Optional.
    end_date: End date in YYYY-MM-DD format. Optional.

Returns:
    Dictionary with the created asset resource name.

Tools revision: d80f65c0.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "customer_id": "<customer_id>",
      "callout_text": "<callout_text>"
    },
    "name": "create_callout_asset"
  }
}

Input Schema

Name	Required	Description	Default
`end_date`	No
`start_date`	No
`customer_id`	Yes
`callout_text`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already mark this as a non-read-only, non-destructive write. The description adds useful behavioral context: creation is inert until linked, it names the linking tools, and it states the return contains the created asset resource name. Duplicate handling, permissions, and rate limits are not covered, but the added context is meaningful.

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?

Front-loads the core action and uses Args/Returns sections, making it easy to scan. It is mostly efficient, though the trailing revision line and the return-value sentence are somewhat redundant given the output schema.

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?

For a four-parameter asset-creation tool with annotations and an output schema, the description covers purpose, linking prerequisites, parameter constraints, and the return. The remaining omissions—permissions and error behavior—are not essential to selecting and invoking it correctly.

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 description coverage is 0%, so the description must carry parameter meaning; it documents all four parameters, including customer_id as digits-only, callout_text max 25 characters, and start/end date as optional YYYY-MM-DD values. It stops short of explaining date inclusivity, timezone, or scheduling behavior, but the core semantics are supplied.

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?

Opens with a specific verb and resource ('Creates a callout asset') and clarifies what a callout is with examples such as 'Free Shipping' and '24/7 Support'. This distinguishes it from the many create_* asset siblings without needing to open the schema.

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?

Explains the prerequisite flow clearly: creating the asset changes no ad, and it appears only after linking via link_asset_to_campaign, link_asset_to_ad_group, or link_assets_to_customer. It does not explicitly compare callouts to other asset types like sitelinks or text assets, so it stops short of full when/when-not guidance.

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

All AdCopilot tools Inspect

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

Need Help?