Skip to main content
Glama

google_ads_keywords_pause

Pause a Google Ads keyword non-destructively, preserving quality score and historical stats. Resume anytime, making it safer than removal for temporary campaign changes.

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, the description fully carries behavioral disclosure. It states the operation is non-destructive, preserves quality score and historical stats, returns criterion ID and new status, and is not automatically reversible. This is exemplary transparency for a mutation tool.

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 four sentences, each adding meaningful information: purpose, non-destructive nature, return value, rollback advice, and sibling distinction. It is information-dense without redundancy or fluff.

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?

Despite having no output schema and no annotations, the description covers the operation's purpose, effects, return value, reversibility, and alternatives. For a simple pause tool, it is fully self-contained and does not leave the agent guessing.

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 itself adds little about the parameters beyond what the schema already documents, but the schema descriptions are complete, so no deduction below baseline is warranted.

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 'Sets the status of a single keyword criterion to PAUSED', which is a specific verb+resource+state. It distinguishes from the sibling google_ads_keywords_remove by explicitly recommending pause for temporary suspensions, making the purpose unmistakable.

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?

Explicit guidance is provided: 'Use this instead of google_ads_keywords_remove whenever the suspension might be temporary.' It also gives the resumption path via google_ads_keywords_add and advises recording before-state for rollback, making the when-to-use clear.

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