Skip to main content
Glama

google_ads_conversions_create

Create a new Google Ads conversion action with a required name and optional type, category, and value settings. The action is enabled by default.

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
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.
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.
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.
view_through_lookback_window_daysNoView-through attribution window in days (1-30). Server-side validated.
click_through_lookback_window_daysNoClick-through attribution window in days (1-90). Server-side validated — invalid values raise ValueError.
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses that the action is persisted with status ENABLED by default, is mutating, and reversible. Also mentions name length constraint and category default. Could add auth or rate limits but covers key 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is concise and front-loaded with purpose and return value. Covers all key points without redundancy. Could be slightly more structured but efficient.

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 8 parameters, 100% schema coverage, and no output schema, the description covers creation, mutation, reversibility, and key parameter defaults. Lacks mention of prerequisites or rate limits but is sufficiently complete for a creation tool with a rich schema.

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 100%, but description adds significant value: clarifies type options (offline vs call conversions), category impact on smart bidding, default_value usage, and lookback window validation. Goes beyond schema to guide parameter choices.

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?

Clearly states 'Create a new Google Ads conversion action' and specifies the return format. Distinguishes from sibling tools like google_ads_conversions_update and google_ads_conversions_remove.

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 says to use this for creating new conversion actions and directs to update/remove for modifications. Mentions reversibility via update with status='REMOVED' or remove.

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