Skip to main content
Glama

google_ads_conversions_update

Update fields such as name, category, status, or attribution windows on an existing Google Ads conversion action using a partial update that only modifies specified fields.

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).
Behavior4/5

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

Clearly explains partial update behavior ('only the fields you pass are modified, the rest are preserved') and return value ({resource_name}). With no annotations, this covers key behavioral aspects adequately, though could mention authentication or rate 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?

Description is concise (4 sentences) and well-structured, front-loading the action and providing essential details without redundancy. 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?

Given 9 parameters, partial update concept, and no output schema, the description covers all necessary context: behavior, error condition, return value, and alternative for deletion. No significant gaps.

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 good descriptions. The description adds value by listing the updatable fields in a sentence and explaining customer_id fallback and how to obtain conversion_action_id. This reinforces and provides context beyond the 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?

Description clearly states 'Update fields on an existing Google Ads conversion action' with specific verb and resource. Distinguishes from siblings by mentioning delete/archive via status 'REMOVED' or separate tool 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 states when to use this tool vs alternatives: 'To delete/archive an action use status "REMOVED" here or call google_ads_conversions_remove.' Also warns that at least one updatable field must be supplied or ValueError is raised.

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