Google Ads MCP Server

create_responsive_search_ad

Create responsive search ads for Google Search campaigns using multiple headlines, descriptions, and landing URLs so Google can test combinations. Enabled ads return a preview before confirmation.

Instructions

Create a Responsive Search Ad (RSA) for Search campaigns.

Google will automatically test combinations of headlines and descriptions.

Safety: an ENABLED ad returns a preview first; call again with confirm=True.
A PAUSED ad is created immediately.

Args:
    customer_id: Google Ads customer ID.
    ad_group_id: Ad group ID (must be in a Search campaign).
    headlines: 3-15 headline strings (max 30 chars each).
    descriptions: 2-4 description strings (max 90 chars each).
    final_urls: List of landing page URLs (at least one required).
    path1: Optional display URL path 1 (max 15 chars).
    path2: Optional display URL path 2 (max 15 chars, requires path1).
    status: Ad status -- 'ENABLED' (default) or 'PAUSED'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "customer_id": "<customer_id>",
      "ad_group_id": "<ad_group_id>",
      "headlines": "<headlines>",
      "descriptions": "<descriptions>",
      "final_urls": "<final_urls>"
    },
    "name": "create_responsive_search_ad"
  }
}

Input Schema

Name	Required	Default
`path1`	No
`path2`	No
`status`	No	ENABLED
`confirm`	No
`headlines`	Yes
`final_urls`	Yes
`ad_group_id`	Yes
`customer_id`	Yes
`descriptions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 11, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing a two-phase execution model: an ENABLED ad returns a preview and requires a second call with confirm=True, while a PAUSED ad is created immediately. This is exactly the kind of non-obvious mutation behavior annotations (destructiveHint=false, idempotentHint=false) cannot convey, and it prevents accidental creation.

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?

Front-loaded with purpose, then the safety model, then a compact parameter list. Every sentence carries information the agent needs; nothing is restated from the tool name or schema, and the preview/confirm warning is placed prominently rather than buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter mutation with no output schema, the definition covers purpose, safety flow, and all parameter constraints, and it notes the ad group must belong to a Search campaign. Minor gap: it does not describe what the returned preview contains or how a caller should interpret it before confirming.

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 description coverage is 0%, so the description carries the full burden — and it does, documenting all nine parameters with counts (3-15 headlines, 2-4 descriptions), length limits (30/90/15 chars), the path2-requires-path1 dependency, the status values, and the confirm flag. An agent could call this correctly without reading the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Create a Responsive Search Ad (RSA)' — and scopes it to 'Search campaigns', which implicitly separates it from the responsive display, demand gen, and video ad creation siblings. It stops short of naming an alternative outright, so the differentiation is inferential rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for when this is the right tool (Search campaigns) and explains the operational choice between status='ENABLED' (preview then confirm) and status='PAUSED' (immediate creation). No explicit 'do not use this when...' guidance or sibling routing, but the conditions are concrete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server