AdCopilot

Google Ads: create conversion action

create_conversion_action

Creates a Google Ads conversion action (what the account counts as a result) and returns the conversion ID and label its website tag needs.

Only type WEBPAGE can be created: a result counted by a Google Ads
conversion tag on the website. Stage that tag in Tag Manager with the
returned conversion_id and conversion_label (the "Google Ads Conversion
Tracking" tag, fired on the sign-up / thank-you trigger); nothing is
counted until the user publishes the Tag Manager container.

Analytics-imported types (GOOGLE_ANALYTICS_4_CUSTOM, _PURCHASE) cannot be
created through the Google Ads API and are refused with an explanation.

This tool creates one ENABLED action and changes nothing else: it never
edits, demotes or removes an existing conversion action or goal.
primary_for_goal has no default on purpose — a primary action is one the
account's bidding aims for, so ask the user and pass their answer.

Args:
    customer_id: The Google Ads customer ID (numbers only, no hyphens).
    name: The conversion action's name, unique in the account
        (e.g. "Sign-up (website)").
    category: What the result is. One of: SIGNUP, SUBMIT_LEAD_FORM,
        PURCHASE, CONTACT, BOOK_APPOINTMENT, REQUEST_QUOTE, SUBSCRIBE_PAID,
        BEGIN_CHECKOUT, ADD_TO_CART, DOWNLOAD, GET_DIRECTIONS,
        OUTBOUND_CLICK, PAGE_VIEW, DEFAULT.
    primary_for_goal: True makes this a primary action — campaigns that
        bid for conversions aim for it. False records it as secondary
        (reported, not bid on). Required: pass what the user chose.
    type: The conversion action type. Only WEBPAGE is supported.
    counting_type: ONE_PER_CLICK (one result per ad click — right for
        sign-ups and leads) or MANY_PER_CLICK (every result — right for
        purchases). Defaults to MANY_PER_CLICK for PURCHASE and
        ONE_PER_CLICK for every other category.
    default_value: The value of one result, in the account's currency
        (a plain amount, not micros). Optional; no value is set if omitted.
    default_currency_code: ISO 4217 currency code for default_value,
        e.g. the account's own currency. Optional.
    always_use_default_value: True always records default_value, ignoring
        any value the tag sends. Optional.
    click_through_lookback_window_days: How many days after an ad click a
        result still counts (1-90). Optional; Google's default if omitted.

Returns:
    Dictionary with the new action's resource name and id, its
    conversion_id / conversion_label / send_to for the website tag, the
    other enabled primary actions already in this category (read only),
    and whether the account's goal for this category is biddable.

Tools revision: 5c9bea8f.

Input Schema

TableJSON Schema

Name	Required	Default
`name`	Yes
`type`	No	WEBPAGE
`category`	Yes
`customer_id`	Yes
`counting_type`	No
`default_value`	No
`primary_for_goal`	Yes
`default_currency_code`	No
`always_use_default_value`	No
`click_through_lookback_window_days`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the annotations: states it creates exactly one ENABLED action, 'changes nothing else', and never edits/demotes/removes existing actions or goals — which confirms the destructiveHint=false and idempotentHint=false hints in concrete terms. It also discloses the side-effect caveat that no conversions are counted until the Tag Manager container is published.

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-loaded: the core action, the WEBPAGE-only constraint, and the downstream Tag Manager requirement all come before the parameter list. The Args block repeats a little (e.g. primary_for_goal's meaning appears twice), but given 0% schema coverage that verbosity is functional rather than wasteful.

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 10-parameter mutation with an output schema present, the description covers creation semantics, defaults, side effects, failure modes, and the post-creation workflow the agent must drive. Nothing needed to invoke it correctly or to hand its result to gtm_create_tag 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 coverage is 0%, so the description carries the full burden and does: customer_id format (digits, no hyphens), name uniqueness, the full category enum, the meaning and bidding consequence of primary_for_goal, the unit gotcha for default_value ('a plain amount, not micros'), ISO 4217 for the currency code, per-category counting_type defaults, and the 1-90 range for the lookback window.

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 Google Ads conversion action') and immediately parenthesizes what a conversion action is, plus states that the return carries the conversion_id/label for the website tag. It is clearly distinguishable from GA4-side conversion tools (ga4_create_conversion_event) and from read-only siblings like conversion_setup_audit.

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 scopes what is creatable ('Only type WEBPAGE'), states an exclusion with rationale ('Analytics-imported types ... cannot be created through the Google Ads API and are refused with an explanation'), and names the follow-on path (stage via Tag Manager using the returned ids, nothing counted until publish). It even instructs the agent to ask the user for primary_for_goal rather than guessing.

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?