Skip to main content
Glama

google_ads_rsa_assets_analyze

Analyze Responsive Search Ad asset performance in a Google Ads campaign: split headlines and descriptions by performance label and key metrics.

Instructions

Split Responsive Search Ad asset performance within a Google Ads campaign into headlines and descriptions. Returns {campaign_id, period, headlines:[{text, performance_label ('BEST'|'GOOD'|'LOW'|'POOR'|'LEARNING'|'PENDING'|'UNKNOWN'), impressions, clicks, conversions, cost, ctr (percent)}], descriptions (same shape), best_headlines (performance_label == 'BEST'), worst_headlines ('LOW'|'POOR'), best_descriptions, worst_descriptions, insights:[strings]}. Rows sorted by impressions descending. Read-only. For an audit version with replacement recommendations use google_ads_rsa_assets_audit; for ad-level A/B use google_ads_ad_performance_compare.

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?

Despite no annotations, the description fully discloses behavior: read-only nature, sorted by impressions descending, full output structure with performance labels and their meanings, groups of best/worst assets, and insights array. No contradictions.

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 well-structured sentences: first defines purpose and output shape, second provides usage guidelines and alternatives. No wasted words, all information earns its place.

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 3 parameters, no output schema, and 80+ sibling tools, the description fully specifies output structure, parameter guidance, and differentiation from related tools. Complete for a complex RSA analysis tool.

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?

With 100% schema coverage, the description adds value by providing usage context for period parameter (short vs long windows), fallback behavior for customer_id, and guidance on obtaining campaign_id via another tool. Exceeds baseline.

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 splits RSA asset performance into headlines and descriptions. The verb 'Split' is specific and the resource is clearly identified. It distinguishes from sibling tools like google_ads_rsa_assets_audit and google_ads_ad_performance_compare.

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 when to use this tool (read-only analysis) and when to use alternatives ('audit version with replacement recommendations' and 'ad-level A/B comparison'). Provides clear context with sibling tool names.

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