Skip to main content
Glama
AdLoop: Google Ads, Reddit Ads & GA4

AdLoop: Google Ads, Reddit Ads & GA4

Draft a conversion action

draft_create_conversion_action

Draft a new Google Ads conversion action and return a preview with a plan_id, so you can review and confirm before any changes apply.

Instructions

Draft a new Google Ads ConversionAction — returns a PREVIEW.

Returns a preview with a plan_id (plus warnings where relevant); nothing changes until confirm_and_apply applies it. SMART_CAMPAIGN_* and GOOGLE_HOSTED types are auto-managed by Google and rejected with MUTATE_NOT_ALLOWED.

Google Ads API: https://developers.google.com/google-ads/api/docs/start

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": {
      "name": "<name>",
      "type_": "<type_>"
    },
    "name": "draft_create_conversion_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesConversion action name as it appears in Google Ads. Required.
type_YesConversionActionType enum value, e.g. AD_CALL, WEBSITE_CALL, WEBPAGE, WEBPAGE_CODELESS, GOOGLE_ANALYTICS_4_CUSTOM, GOOGLE_ANALYTICS_4_PURCHASE, UPLOAD_CALLS, UPLOAD_CLICKS.
categoryNoConversionActionCategory enum value, e.g. PHONE_CALL_LEAD, SUBMIT_LEAD_FORM, PURCHASE, ... (default DEFAULT).DEFAULT
customer_idNoGoogle Ads customer ID (digits, dashes allowed). Defaults to the configured account.
counting_typeNoONE_PER_CLICK (default; one conversion per click, typical for lead gen) or MANY_PER_CLICK (every conversion counts, typical for ecommerce).ONE_PER_CLICK
currency_codeNo3-letter ISO 4217 currency code for default_value (default USD).USD
default_valueNoValue attributed to each conversion, in currency_code units (not micros). Must be >= 0. A positive default_value with always_use_default_value=False is a legal "fallback" config: the preview warns but does NOT flip the flag.
primary_for_goalNoTrue (default) makes it a Primary action that Smart Bidding optimizes toward; False makes it Secondary (recorded only).
attribution_modelNoAttributionModel enum value, e.g. GOOGLE_SEARCH_ATTRIBUTION_DATA_DRIVEN. Empty leaves Google's default.
always_use_default_valueNoTrue ignores transaction values from the tag/import and always uses default_value; False uses default_value only as a fallback when no value is supplied.
view_through_window_daysNoView-through attribution window in days, 1-30. 0 leaves Google's default.
click_through_window_daysNoClick-through attribution window in days, 1-90. 0 leaves Google's default.
phone_call_duration_secondsNoMinimum call length in seconds for a call to count; only meaningful for call conversions (PHONE_CALL_LEAD category). 0 leaves Google's default.
include_in_conversions_metricNoIMMUTABLE — Google derives it from primary_for_goal and the category's goal, so this value is not sent.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.42.0
    • changedInput schema / properties / include_in_conversions_metric / description
      Previous value: -"IMMUTABLE on create — Google derives it\nfrom the category, so this value is not sent; change it later via\ndraft_update_conversion_action."New value: +"IMMUTABLE — Google derives it from\nprimary_for_goal and the category's goal, so this value is not sent."
  2. Changed14 schema fields changedv0.27.1
    • addedInput schema / properties / always_use_default_value / description
      Added value: +"True ignores transaction values from the\ntag/import and always uses default_value; False uses default_value\nonly as a fallback when no value is supplied."
    • addedInput schema / properties / attribution_model / description
      Added value: +"AttributionModel enum value, e.g.\nGOOGLE_SEARCH_ATTRIBUTION_DATA_DRIVEN. Empty leaves Google's default."
    • addedInput schema / properties / category / description
      Added value: +"ConversionActionCategory enum value, e.g. PHONE_CALL_LEAD,\nSUBMIT_LEAD_FORM, PURCHASE, ... (default DEFAULT)."
    • addedInput schema / properties / click_through_window_days / description
      Added value: +"Click-through attribution window in days,\n1-90. 0 leaves Google's default."
    • addedInput schema / properties / counting_type / description
      Added value: +"ONE_PER_CLICK (default; one conversion per click, typical\nfor lead gen) or MANY_PER_CLICK (every conversion counts, typical\nfor ecommerce)."
    • addedInput schema / properties / currency_code / description
      Added value: +"3-letter ISO 4217 currency code for default_value\n(default USD)."
    • addedInput schema / properties / customer_id / description
      Added value: +"Google Ads customer ID (digits, dashes allowed). Defaults\nto the configured account."
    • addedInput schema / properties / default_value / description
      Added value: +"Value attributed to each conversion, in currency_code\nunits (not micros). Must be >= 0. A positive default_value with\nalways_use_default_value=False is a legal \"fallback\" config: the\npreview warns but does NOT flip the flag."
    • addedInput schema / properties / include_in_conversions_metric / description
      Added value: +"IMMUTABLE on create — Google derives it\nfrom the category, so this value is not sent; change it later via\ndraft_update_conversion_action."
    • addedInput schema / properties / name / description
      Added value: +"Conversion action name as it appears in Google Ads. Required."
    • addedInput schema / properties / phone_call_duration_seconds / description
      Added value: +"Minimum call length in seconds for a call\nto count; only meaningful for call conversions (PHONE_CALL_LEAD\ncategory). 0 leaves Google's default."
    • addedInput schema / properties / primary_for_goal / description
      Added value: +"True (default) makes it a Primary action that Smart\nBidding optimizes toward; False makes it Secondary (recorded only)."
    • addedInput schema / properties / type_ / description
      Added value: +"ConversionActionType enum value, e.g. AD_CALL, WEBSITE_CALL,\nWEBPAGE, WEBPAGE_CODELESS, GOOGLE_ANALYTICS_4_CUSTOM,\nGOOGLE_ANALYTICS_4_PURCHASE, UPLOAD_CALLS, UPLOAD_CLICKS."
    • addedInput schema / properties / view_through_window_days / description
      Added value: +"View-through attribution window in days,\n1-30. 0 leaves Google's default."
  3. Addedv0.13.3

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description discloses the preview-only semantics, the returned plan_id and warnings, and the specific rejection code MUTATE_NOT_ALLOWED for Google-managed types. For a mutation tool this is exactly the extra context an agent needs to avoid assuming the change is live.

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?

Three short sentences: what it does, what it returns and how it gets applied, and what gets rejected. The preview caveat is front-loaded where it matters most, and nothing is repeated from the 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?

With 14 parameters, an output schema, and full annotation coverage, the remaining description burden is behavioral rather than structural. The definition covers the mutation-safety story, the confirmation path, and the failure mode, which is everything an agent needs to call 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 coverage is 100%, so the baseline is 3, but the description adds a real constraint on the required type_ parameter by naming the enum families that are auto-managed and will be rejected. It adds no further guidance on the other twelve parameters, which is acceptable given the schema documents them thoroughly.

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?

The description opens with a specific verb and resource ("Draft a new Google Ads ConversionAction") and immediately qualifies the outcome ("returns a PREVIEW"), so the agent knows this is a staging operation rather than a live mutation. That framing cleanly separates it from confirm_and_apply and from the update/remove draft siblings.

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?

It explicitly states the workflow condition: nothing changes until confirm_and_apply applies it, which tells the agent both when to call this tool and what the follow-up is. It also names the case where the call is refused (SMART_CAMPAIGN_* and GOOGLE_HOSTED types), though it does not spell out when to prefer draft_update_conversion_action over creating a new action.

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

Deploy Server

Other Tools