Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_conversions_create

Create a new Google Ads conversion action to track customer actions. Configure type, category, value, and attribution windows. Returns the new conversion action resource ID.

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.
reasonNoWhy this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.20.0
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Why this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.",
+  "maxLength": 500,
+  "type": "string"
+}
  2. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv0.10.11
  4. Removedv0.10.9
  5. Addedv0.9.12
  6. Removedv0.9.6
  7. Addedv0.9.2
  8. Removedv0.9.1
  9. Addedv1.0.5

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full transparency burden and delivers: it discloses that the tool is mutating, that the action is persisted with status ENABLED by default, that the operation is reversible through specific tools, and what resource_name the call returns. This is strong behavioral disclosure for a create operation.

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?

The description is compact and front-loaded with the core action and return value. A few sentences repeat schema constraints (name length, category default), but the overall text remains efficient and every sentence serves a useful routing or behavior purpose.

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 9-parameter create operation with no output schema and no annotations, the description covers the essential contextual gaps: return format, persistence side effect, default status, reversibility, and alternative tool. The input schema covers parameter details, making the combined package complete for an agent to invoke correctly.

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 the schema already documents all nine parameters with rich detail. The tool description adds marginal value by restating the 256-character name limit and the DEFAULT category, but these are already present in the schema, so no additional semantic burden is placed on the description.

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 object: 'Create a new Google Ads conversion action,' and it immediately distinguishes itself from update/remove operations by describing the created row's resource_name return shape. This clearly differentiates the tool from the many Google Ads siblings in the provided list.

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?

The description explicitly states when to use an alternative: 'For updating an existing action use google_ads_conversions_update.' It even mentions reversibility via update with status='REMOVED' or via google_ads_conversions_remove, giving an agent concrete routing and follow-up guidance.

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