Skip to main content
Glama

google_ads_keywords_audit

Audit a Google Ads campaign's keyword portfolio to identify pause candidates, bid-raise opportunities, match-type tightening needs, and unused keyword ideas. Read-only recommendations.

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
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.
campaign_idYesCampaign to audit.
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.
Behavior4/5

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

Despite no annotations, the description discloses read-only nature, that recommendations are not applied, and details the content of each recommendation item (criterion_id, text, spend, conversions, reason). It adds behavioral context beyond the schema, though it could mention response size or pagination.

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?

Single dense paragraph with front-loaded purpose, then list of recommendation categories, item fields, and read-only note. Every sentence is essential; no waste.

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?

No output schema, but the description sufficiently describes the return structure (grouped recommendations with specific fields). It covers available parameters and their defaults/functions. The description is complete for an analysis tool with clear follow-up actions.

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 baseline is 3. The description adds minimal extra meaning: it notes target_cpa is used to score efficiency and period accepts specific formats, but these are already in the schema. No new parameter semantics are added.

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 holistic keyword-portfolio audit for a campaign, listing specific recommendation types (pause, bid-raise, match-type-tighten, unused ideas). This differentiates it from sibling tools like google_ads_keywords_diagnose or google_ads_keywords_list by focusing on audit and grouped recommendations.

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, and directs the agent to materialize them via google_ads_keywords_pause, add, or negative_keywords.add. This provides clear when-to-use and alternative actions.

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