Skip to main content
Glama

google_ads_keywords_audit

Audit a Google Ads campaign's keyword portfolio to identify pause, bid-raise, and match-type-tighten candidates along with unused keyword ideas, including spend, conversions, and reasons for each recommendation.

Instructions

Runs a holistic keyword-portfolio audit for a campaign and returns grouped recommendations: pause candidates (zero-spend or zero-conversion), bid-raise candidates (below first-page bid), match-type-tighten candidates (broad stealing spend), and unused keyword-planner ideas. Each item includes criterion_id, text, spend, conversions, and a reason string. Read-only — recommendations are not applied. Materialize accepted ones via google_ads_keywords_pause / add / negative_keywords.add.

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.
campaign_idYesCampaign to audit.
periodNoAnalysis window. Accepts 'LAST_7_DAYS', 'LAST_14_DAYS', 'LAST_30_DAYS' (default), or 'YYYY-MM-DD..YYYY-MM-DD'.
target_cpaNoTarget CPA in the account's currency used to score efficiency. Falls back to the campaign's configured target_cpa when omitted.
Behavior4/5

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

With no annotations, the description fully discloses that the tool is read-only and lists the output fields. It does not mention potential rate limits or permissions, but the 'Read-only' label covers safety. Could include more on error conditions but is sufficient.

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?

Two sentences: first captures purpose and outputs, second adds detail and actionable next steps. Front-loaded and no unnecessary words.

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?

Given the tool has full schema descriptions and no output schema, the description adequately explains the output structure and read-only nature. Sibling tools for applying recommendations are referenced, making the overall usage complete.

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%, so the schema already explains the parameters thoroughly. The description adds no new parameter-level information beyond what the schema provides, meeting the baseline expectation.

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 it runs a keyword-portfolio audit and lists specific recommendation groups (pause, bid-raise, match-type-tighten, unused ideas). It distinguishes from sibling tools by focusing on holistic audit rather than listing, suggesting, or mutating keywords.

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 states the tool is read-only and recommendations are not applied, directing the agent to use google_ads_keywords_pause / add / negative_keywords.add for materialization. Provides clear context for when to use (holistic audit) and what to do next.

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