Skip to main content
Glama

google_ads_conversions_remove

Remove a Google Ads conversion action to permanently stop counting conversions while preserving historical data.

Instructions

Archive (status=REMOVED) a Google Ads conversion action. Returns {resource_name} of the removed row. Destructive — historical data remains but the action stops counting toward 'Conversions'. Re-enabling requires google_ads_conversions_update with status='ENABLED'. For soft-hide that keeps the row visible use google_ads_conversions_update with status='HIDDEN'.

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

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

Discloses destructive nature (stops counting, historical data remains), return value, and reversion method. Lacks authorization or rate limit info, but no annotations exist to carry burden.

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?

Concise, front-loaded sentences. Every sentence adds value 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?

Complete for a removal tool: explains behavior, return value, and alternatives. No missing critical information given no output schema.

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 provides full descriptions; description adds context for obtaining conversion_action_id via google_ads_conversions_list, aiding agent understanding beyond 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?

Clearly states the action: archive a conversion action by setting status=REMOVED. Distinguishes from sibling tools like google_ads_conversions_update which can set ENABLED or HIDDEN.

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 provides when to use this tool and when not to, offering alternatives: use google_ads_conversions_update with HIDDEN for soft-hide, and re-enable via update with ENABLED.

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