google-ads-mcp

Overview Schema Source Related Servers Discussions Admin

create_responsive_search_ad

Create responsive search ads for Google Ads Search campaigns by supplying headlines, descriptions, and final URLs, letting Google automatically test combinations to optimize performance.

Instructions

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

Google will automatically test combinations of headlines and descriptions.

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
`headlines`	Yes
`final_urls`	Yes
`ad_group_id`	Yes
`customer_id`	Yes
`descriptions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 4, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already indicate this is a non-read-only, non-idempotent, non-destructive write operation. The description adds useful behavioral context: 'Google will automatically test combinations of headlines and descriptions.' It does not elaborate on side effects, response behavior, or failure modes, but given annotation coverage the description provides reasonable added value.

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 with a brief purpose statement, a useful behavioral note, and a clean argument list. Every sentence and line adds necessary constraint information without redundancy or filler.

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 tool with 8 parameters, all parameter semantics are covered, including defaults and dependencies. There is no output schema and the description does not mention return values, which is a minor gap, but the information needed to invoke the tool correctly is present and complete.

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%, yet the description thoroughly documents every parameter: customer_id, ad_group_id with a Search campaign constraint, headlines count/length limits, descriptions count/length limits, final_urls requirement, path constraints including the path2-requires-path1 rule, and status enum values. This fully compensates for the schema's lack of descriptions.

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 states a specific action ('Create a Responsive Search Ad') and clearly scopes it to 'Search campaigns.' This distinguishes it from sibling tools like create_responsive_display_ad and create_video_ad, so an agent can tell them apart without opening schemas.

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?

The description gives clear context by specifying that the ad group 'must be in a Search campaign,' which implies this tool is for Search campaign ad creation. However, it does not explicitly name alternative tools or state when not to use this tool, so it stops short of full usage differentiation.

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

Deploy Server