Skip to main content
Glama

google_ads_keywords_pause

Pauses a Google Ads keyword without removing it, preserving quality score and historical stats for easy resumption.

Instructions

Sets the status of a single keyword criterion to PAUSED. Lightweight and non-destructive — quality score and historical stats are preserved, and the keyword can be resumed by calling google_ads_keywords_add with the same text+match_type (or re-enabled via the Google Ads UI). Returns the criterion ID and new status. Not automatically reversible — record before-state with mureo_state_action_log_append if you may need to roll back. Use this instead of google_ads_keywords_remove whenever the suspension might be temporary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ad_group_idYesParent ad group ID.
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.
criterion_idYesKeyword criterion ID as returned by google_ads_keywords_list.
Behavior5/5

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

With no annotations provided, the description fully discloses the tool's behavior: it is lightweight and non-destructive, preserves quality score and historical stats, returns criterion ID and new status, and notes it is not automatically reversible. This provides sufficient transparency for an AI agent to understand side effects and prerequisites.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise at three sentences, with the key action and benefits front-loaded. Every sentence adds value. Slightly verbose due to the rollback suggestion, but still efficient.

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?

For a simple pause action, the description covers return values, rollback consideration, and distinction from alternative tools. The optional customer_id fallback is documented in the schema, so omitting it here is acceptable. Nearly complete for the tool's complexity.

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% with good descriptions for each parameter. The description does not add new meaning beyond the schema (e.g., it only mentions criterion_id's source, which is already in the schema). Baseline 3 is appropriate as the schema does the heavy lifting.

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's action (sets status to PAUSED), explicitly distinguishes it from the sibling tool google_ads_keywords_remove by emphasizing temporary suspension, and mentions resumption via google_ads_keywords_add or UI. The verb+resource combination is specific and unambiguous.

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 provides explicit guidance on when to use this tool ('whenever the suspension might be temporary') and when not (avoid remove). It also advises on recording before-state for rollback, giving clear context and alternatives.

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