AdCopilot

Google Ads: create call asset

create_call_asset

Creates a call 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.

Call assets add a phone number to your ad, allowing users to call directly.

Args:
    customer_id: The Google Ads customer ID (numbers only, no hyphens).
    country_code: Two-letter country code (e.g., "US", "GB", "IN").
    phone_number: The phone number string.
    call_conversion_reporting_state: One of: DISABLED, USE_ACCOUNT_LEVEL_CALL_CONVERSION_ACTION,
        USE_RESOURCE_LEVEL_CALL_CONVERSION_ACTION. Default: DISABLED.

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>",
      "country_code": "<country_code>",
      "phone_number": "<phone_number>"
    },
    "name": "create_call_asset"
  }
}

Input Schema

Name	Required	Default
`customer_id`	Yes
`country_code`	Yes
`phone_number`	Yes
`call_conversion_reporting_state`	No	DISABLED

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent mutation; the description adds the important behavioral fact that the asset is inert until linked. That is exactly the kind of consequence an agent needs before calling. It does not cover permissions, duplicate-phone handling, or failure modes, keeping it below a 5.

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 key constraint (no ad changes until linked) is front-loaded, and the Args block is compact. The Returns section partially duplicates the output schema and the Args block repeats schema titles, but given 0% schema coverage that repetition is doing real work.

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 creation tool with annotations and an output schema, the description covers purpose, post-conditions, link prerequisites, and every parameter's expected format. Nothing an agent needs in order to invoke it correctly is missing.

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?

Schema description coverage is 0%, so the description carries the full burden and does so: customer_id format (numbers only, no hyphens), country_code as a two-letter code with examples, phone_number as a string, and the four allowed call_conversion_reporting_state values plus the DISABLED default. All four parameters gain meaning beyond the bare schema titles.

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+resource ("Creates a call asset") and immediately scopes the result ("can be linked to campaigns or ad groups"). Among the many create_*_asset siblings, the resource name distinguishes it clearly 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?

Explicitly states that creation alone changes no ad and names the three follow-up tools (link_asset_to_campaign, link_asset_to_ad_group, link_assets_to_customer) required to make it live. It stops short of saying when a call asset is preferable to other asset types, but the sequencing guidance is unusually strong.

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?