Skip to main content
Glama

google_ads_creative_research

Retrieve all data required to create or update Google Ads responsive search ads for a campaign: landing page analysis, top performing existing ads, search term insights, keyword suggestions, and existing keywords.

Instructions

Collect every input an LLM needs to draft or refresh Google Ads creative for a single campaign. Returns {campaign_id, url, lp_analysis (same shape as google_ads_landing_page_analyze), existing_ads:[{ad_id, headlines, descriptions, final_urls, impressions, clicks, conversions, ctr}] (top 5 RSA ads by impressions, REMOVED excluded), search_term_insights:{high_cv_terms (top 10 by conversions), high_click_terms (top 10 by clicks), total_terms}, keyword_suggestions (KeywordPlanIdeaService output for up to 5 seeds derived from LP title + h1 + meta_description), existing_keywords (list_keywords output), context_summary (string)}. Any failing sub-step is replaced with the literal string '取得失敗' so the envelope never raises. Side effect: one outbound LP fetch (same SSRF policy as google_ads_landing_page_analyze) plus several GAQL queries. For just the LP use google_ads_landing_page_analyze; for just RSA asset diagnostics 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.
urlYesAbsolute landing page URL to analyze (http:// or https:// only, e.g. 'https://example.com/lp/'). SSRF-protected — private-range, loopback, and cloud-metadata hosts are rejected.
ad_group_idNoOptional ad group ID as a numeric string (e.g. '145680123456') to restrict results to a single ad group. Omit to include every ad group matching the campaign filter.
Behavior4/5

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

No annotations provided, so description carries full burden. It details side effects (LP fetch, GAQL queries), error handling (failure replaced with literal), and SSRF protection. Lacks explicit read-only statement but implies non-destructive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single paragraph with front-loaded purpose. Informative but somewhat dense; could be broken into shorter sentences. Still 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?

For a complex tool with no output schema, the description thoroughly explains return shape, sub-steps, and error behavior, making it complete for agent use.

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 description adds no extra parameter meaning beyond schema descriptions. Baseline 3 is appropriate.

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 collects all inputs needed for creative drafting/refresh, with a specific verb and resource. It distinguishes from siblings by naming alternatives.

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 says when to use alternatives ('For just the LP use google_ads_landing_page_analyze; for just RSA use google_ads_rsa_assets_analyze') and describes side effects.

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