Skip to main content
Glama

google_ads_conversions_create

Create a new Google Ads conversion action to track and measure key business goals. Define the name, type, category, and attribution window to capture conversions from clicks or views.

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?

No annotations provided, so description carries full burden. It discloses mutation, persistence with default status ENABLED, reversibility, and server-side validation for lookback windows. Lacks auth requirements but covers main behavioral aspects.

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?

Description is concise, front-loaded with the core action and return value, followed by behavioral context and sibling reference. Every sentence adds value.

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 creation tool with 8 parameters and no output schema, the description covers mutation, defaults, reversibility, parameter constraints, and return format. It references sibling tools for update/remove, making it contextually complete.

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 coverage is 100%, so baseline is 3. The description adds context for name max length, category default, type default, and default_value example, but mostly repeats schema info.

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 it creates a new Google Ads conversion action, specifies the return format, and distinguishes from sibling tools (google_ads_conversions_update, google_ads_conversions_remove). It is specific about the action being persisted with status ENABLED.

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?

The description explicitly mentions the alternative for updating (google_ads_conversions_update) and removing (google_ads_conversions_remove). It implies creation is for new actions, but does not explicitly state prerequisites or when not to use, which is acceptable.

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