Skip to main content
Glama

google_ads_keywords_pause

Pause a Google Ads keyword while preserving quality score and historical stats. Non-destructive, reversible by resuming or using the UI. Use for temporary suspensions instead of removing.

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. Reversible via rollback_apply. Use this instead of google_ads_keywords_remove whenever the suspension might be temporary.

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.
ad_group_idYesParent ad group ID.
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 discloses behavioral traits: lightweight, non-destructive, preserves quality score and historical stats, resumable via google_ads_keywords_add or UI, returns criterion ID and new status, and reversible via rollback_apply. This exceeds expectations.

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-load the purpose and include all essential information without redundancy. Every sentence earns its place, making it easy for an agent to quickly grasp usage and behavior.

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 simple pause action with 3 parameters and no output schema, the description covers purpose, behavior, return value, reversible action, and comparison to siblings. It is complete given 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?

Input schema covers all 3 parameters with descriptions, so baseline is 3. The description does not add semantic value beyond what the schema provides, but it does mention criterion_id as returned by google_ads_keywords_list, which is already in the schema. No significant enrichment.

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: 'Sets the status of a single keyword criterion to PAUSED.' It specifies the resource (keyword criterion) and distinguishes from siblings like google_ads_keywords_remove and google_ads_keywords_add by mentioning resumption and temporary suspension.

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 advises: 'Use this instead of google_ads_keywords_remove whenever the suspension might be temporary.' It also mentions reversibility via rollback_apply, providing clear guidance on when to use this tool versus 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