Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_conversions_remove

Archive a Google Ads conversion action to stop it counting toward Conversions while preserving historical data. Returns the removed resource name; reactivate by setting status to ENABLED.

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
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.
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.

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.7/5.0
Behavior5/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It clearly warns 'Destructive' and specifies the impact: historical data remains but the action stops counting toward 'Conversions.' It also mentions the return value and the reversibility path, giving agents a complete picture of consequences.

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 three sentences with no redundant phrasing. The core action is front-loaded, followed by consequences and alternatives. Every sentence contributes new, decision-relevant information, and nothing is unnecessary.

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 destructive mutation tool with no annotations or output schema, this description is fully complete. It covers the action, the destructive nature, the impact on metrics, the return value, and the available alternatives. An agent has everything needed to call it correctly and understand the consequences.

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 baseline is 3. The description does not elaborate on parameters beyond what the schema already provides; it correctly leaves parameter details to the schema. No additional semantic value is added in the description, so a 3 is appropriate.

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 'Archive (status=REMOVED) a Google Ads conversion action,' which precisely names the verb, resource, and status. It also distinguishes itself from sibling google_ads_conversions_update by explicitly contrasting with the HIDDEN status alternative, so an agent can immediately identify this tool's unique job.

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 a different tool: 'For soft-hide that keeps the row visible use google_ads_conversions_update with status='HIDDEN'.' It also notes that re-enabling requires update with ENABLED, giving clear routes to alternatives. No ambiguity about when to invoke this tool.

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