Google Ads MCP Server

create_responsive_search_ad

Create a responsive search ad in paused state within an ad group, specifying headlines, descriptions, and final URLs for Google Ads campaigns.

Instructions

Create a responsive search ad (in PAUSED state)

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": {
      "customerId": "<customerId>",
      "adGroupId": "<adGroupId>",
      "headlines": "<headlines>",
      "descriptions": "<descriptions>",
      "finalUrls": "<finalUrls>"
    },
    "name": "create_responsive_search_ad"
  }
}

Input Schema

Name	Required	Description
`adGroupId`	Yes	Ad group ID
`finalUrls`	Yes	Final URLs
`headlines`	Yes	Headlines (3-15, max 30 chars each)
`customerId`	Yes	Google Ads customer ID
`descriptions`	Yes	Descriptions (2-4, max 90 chars each)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Without annotations, the description carries full disclosure burden. It does disclose the important behavioral trait that the ad is created in a PAUSED state, which prevents unintended live serving. However, it does not mention other relevant details such as what happens to existing ads, whether the operation is idempotent, or what the response contains.

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 a single, informative sentence that immediately communicates the action and a key behavioral detail (PAUSED state) without any fluff or redundancy.

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?

With a simple 5-parameter schema fully documented in the schema and a clear one-line description, the tool is adequately specified for an agent to create an RSA. The only notable gap is the lack of any indication of the response format, which might matter given there is no output schema. Still, the essential invocation context is present.

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?

The input schema already provides 100% parameter descriptions, covering constraints like 'Headlines (3-15, max 30 chars each)' and 'Descriptions (2-4, max 90 chars each)'. The description itself adds no parameter-level meaning beyond the schema, so it meets the baseline for high schema coverage.

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 uses the specific verb 'create' and names the exact resource 'responsive search ad', clearly distinguishing it from sibling tools like 'create_ad_group' or 'create_smart_campaign'. The added detail of 'in PAUSED state' further clarifies the tool's behavior.

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

Usage Guidelines3/5

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

The description provides no explicit guidance on when to use this tool versus alternatives like create_smart_campaign or create_performance_max_campaign. Usage is implied by the name and resource type, but no contextual conditions or when-not-to-use are given.

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

Deploy Server