Skip to main content
Glama

google_ads_rsa_assets_audit

Audit Responsive Search Ad assets to identify underperforming headlines and descriptions, then get priority recommendations for replacements per Google's guidance.

Instructions

Audit Responsive Search Ad assets against Google's quantity and quality guidance and emit replacement recommendations. Returns {campaign_id, period, headline_count, description_count, label_distribution:{:count}, best_headlines, worst_headlines, best_descriptions, worst_descriptions, recommendations:[{type ('add_headlines'|'add_descriptions'|'replace_headline'|'replace_description'|'wait_for_data'), priority ('HIGH'|'MEDIUM'|'LOW'), message, asset_text?, performance_label?}], recommendation_count}. HIGH priorities fire when headlines < 8 or descriptions < 3. LOW 'wait_for_data' fires when LEARNING+UNKNOWN > 50% of assets. Read-only; does not modify any assets. For the raw per-asset performance breakdown use google_ads_rsa_assets_analyze.

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 ID as a numeric string without dashes (e.g. '23743184133'). Obtain via google_ads_campaigns_list.
periodNoReporting window for the metrics. Default 'LAST_30_DAYS'. Use a shorter window (LAST_7_DAYS / LAST_14_DAYS) when diagnosing recent changes; use LAST_90_DAYS for trend baselines.
Behavior5/5

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

The description discloses the tool is read-only and does not modify assets. It explains the output structure and priority logic, compensating for missing annotations.

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 well-structured, front-loaded with purpose, then output fields, priority logic, and sibling reference. Every sentence is necessary and concise.

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 no output schema, the description fully explains the return object structure and field meanings. It covers all necessary context for an agent to invoke and interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the description adds context: default period, suggestions for window selection, fallback behavior for customer_id, and how to obtain campaign_id.

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 audits RSA assets against Google's guidance and emits recommendations. It distinguishes from sibling google_ads_rsa_assets_analyze, which provides raw per-asset data.

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 when-to-use (audit for recommendations) and when-not-to (for raw breakdown use analyze). It also explains priority conditions (HIGH/LOW) and read-only nature.

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