Skip to main content
Glama
kLOsk

AdLoop: Google Ads, Reddit Ads & GA4

by kLOsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Draft a conversion action

draft_create_conversion_action

Preview a new Google Ads conversion action before applying it. Define type, category, value, counting, and windows; no changes occur until confirm_and_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

Input Schema

TableJSON 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 on create — Google derives it from the category, so this value is not sent; change it later via draft_update_conversion_action.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. Addedv0.13.3

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: the preview semantics, that a plan_id is returned, that warnings may accompany it, and the specific MUTATE_NOT_ALLOWED rejection for auto-managed types. The annotations only declare safety hints, so this description carries real operational detail.

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 purpose and the preview/rejection facts before the URL. Efficient overall; the trailing Google Ads API link is mildly extraneous but harmless.

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?

Given an output schema exists and annotations cover the safety profile, the description needn't explain return values — yet it still usefully notes plan_id and warnings. The full draft-then-confirm workflow plus the rejection rule makes it complete for this 14-param mutation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all 14 parameters are already well documented in the schema. The description adds no parameter-level detail beyond that, which matches the baseline for a fully-covered 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?

States a specific verb+resource ('Draft a new Google Ads ConversionAction') and immediately clarifies the operation is a preview, not a committed write. This distinguishes it from draft_update_conversion_action and draft_remove_conversion_action among the 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?

Explains the two-step workflow ('nothing changes until confirm_and_apply applies it'), which tells the agent this is the front half of a draft→apply pair. It also names the condition under which the call is rejected (SMART_CAMPAIGN_* and GOOGLE_HOSTED), but it does not explicitly point to sibling update/remove tools for modifying an existing 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