Skip to main content
Glama

google_ads_conversions_update

Update specific fields (name, category, status, default value, attribution windows) on an existing Google Ads conversion action while preserving other settings. Requires at least one field to modify.

Instructions

Update fields on an existing Google Ads conversion action via FieldMask mutate. Returns {resource_name} of the updated row. Mutating — partial update: only the fields you pass are modified, the rest are preserved. At least one updatable field must be supplied (name, category, status, default_value, always_use_default_value, click_through_lookback_window_days, view_through_lookback_window_days) or the call raises ValueError. To delete/archive an action use status 'REMOVED' here or call google_ads_conversions_remove.

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.
conversion_action_idYesConversion action ID as a numeric string (e.g. '987654321'). Obtain via google_ads_conversions_list.
nameNoNew display name (max 256 characters). Omit to leave the name unchanged.
categoryNoNew category. Must match the allowed enum.
statusNoNew status. 'ENABLED' counts toward 'Conversions' column; 'HIDDEN' excludes it from the column but keeps the action; 'REMOVED' archives it.
default_valueNoNew default conversion value in account currency.
always_use_default_valueNoToggle whether default_value always overrides tag-supplied values.
click_through_lookback_window_daysNoNew click-through attribution window in days (1-90).
view_through_lookback_window_daysNoNew view-through attribution window in days (1-30).
Behavior5/5

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

Discloses partial update semantics (only passed fields modified), return value (resource_name), error condition (ValueError if no updatable field), and deletion method (status REMOVED or calling remove tool). No annotations provided, so description fully covers behavioral traits.

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?

The description is concise (3 sentences) and well-structured. It front-loads the purpose, then explains behavior and prerequisites. Every sentence adds essential information without redundancy.

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?

With no output schema, the description properly states the return value (resource_name). It covers all key behaviors: update mechanism, field requirements, deletion options, and lists all updatable fields. Complete for this update tool.

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% with detailed descriptions for each parameter. The description adds value by explaining the partial update context, the mandatory field requirement, and clarifying status meanings (ENABLED, HIDDEN, REMOVED). Slightly above baseline due to added context.

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 updates fields on an existing Google Ads conversion action via FieldMask mutate, specifies return value, and lists updatable fields. It distinguishes itself from siblings like google_ads_conversions_create 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?

Provides explicit when-to-use guidance (update fields), notes prerequisites (at least one updatable field must be supplied), and directs to alternative tool for deletion/archiving (google_ads_conversions_remove). Also explains partial update behavior.

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