Skip to main content
Glama

google_ads_conversions_update

Update existing Google Ads conversion action fields like name, status, category, default value, and attribution windows. Returns the resource name of the updated action.

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

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

With no annotations, the description carries full burden. It explains partial update, required fields, and return value. Could mention idempotency or permissions, but current info is solid.

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?

Three sentences, front-loaded with key purpose, no redundancy. Every sentence serves a distinct purpose.

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?

Covers behavior, error conditions, and alternative tool. Without output schema, return format is implicit but acceptable. Slight gap: no mention of pagination or rate limits, but not critical for an update tool.

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 lists updatable fields but adds no new information beyond schema descriptions. It reinforces but doesn't extend meaning.

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 action (update), the resource (Google Ads conversion action), and the mechanism (FieldMask mutate). It distinguishes from creation and removal tools.

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 describes partial update behavior, required fields, and error condition (ValueError if no updatable field supplied). Also offers alternative for deletion (google_ads_conversions_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