Skip to main content
Glama

google_ads_conversions_create

Create a new conversion action in Google Ads to track website or offline conversions. Customize name, type, category, and attribution windows. Returns the resource name of the newly created conversion action.

Instructions

Create a new Google Ads conversion action. Returns {resource_name:'customers//conversionActions/'} of the newly created row. Mutating — the conversion action is persisted with status ENABLED by default. Reversible via google_ads_conversions_update with status='REMOVED' or google_ads_conversions_remove. Name must be <= 256 characters. Category defaults to 'DEFAULT'. For updating an existing action use google_ads_conversions_update.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idNoGoogle Ads customer ID as a 10-digit string without dashes (e.g. '1234567890'). Optional — falls back to GOOGLE_ADS_CUSTOMER_ID / GOOGLE_ADS_LOGIN_CUSTOMER_ID from the configured credentials when omitted.
nameYesHuman-readable conversion action name shown in the Google Ads UI (e.g. 'Purchase - Checkout Complete'). Required. Max 256 characters.
typeNoConversionActionType enum. Default 'WEBPAGE' (site tag fires). Use 'UPLOAD_CLICKS' for offline-conversion uploads or 'WEBSITE_CALL' for call conversions.
categoryNoConversion category. Default 'DEFAULT'. Smart bidding uses this to group similar goals.
default_valueNoDefault monetary conversion value in account currency (e.g. 5000 = ¥5,000). Used when the site tag does not send a value.
always_use_default_valueNoWhen true, always use default_value even if the site tag sends a dynamic value.
click_through_lookback_window_daysNoClick-through attribution window in days (1-90). Server-side validated — invalid values raise ValueError.
view_through_lookback_window_daysNoView-through attribution window in days (1-30). Server-side validated.
Behavior4/5

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

Discloses mutating nature, default ENABLED status, reversibility, and return value. Schema descriptions cover validation, but main description could mention more about side effects or limits.

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?

Two sentences plus brief statements, no fluff. Every sentence adds essential information. Efficient and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, description explains return value and key behaviors. Covers creation, defaults, reversibility, and related tools. Could mention that resource name is used for future updates, but overall sufficient.

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 description need not repeat details. However, it adds value by stating default values for category (DEFAULT) and type (WEBPAGE), and gives usage hints for type parameter beyond 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?

The description clearly states the tool 'Create a new Google Ads conversion action' and specifies the return format. It distinguishes from siblings by explicitly directing to use google_ads_conversions_update for updating existing actions.

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?

Provides when to use (creating new) and when not to (updating existing), mentions reversibility via update/remove, and notes defaults. Lacks explicit exclusion of other conversion tools, but sibling names imply context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly/mureo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server