Google Ads MCP Server

create_responsive_display_ad

Creates a responsive display ad in a Google Ads Display campaign using headlines, descriptions, images, logos, business name, and final URLs; enabled ads return a preview before confirmation.

Instructions

Create a Responsive Display Ad for Display campaigns.

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 Display campaign).
    headlines: 1-5 short headlines (max 30 chars each).
    long_headline: Long headline (max 90 chars).
    descriptions: 1-5 descriptions (max 90 chars each).
    marketing_images: List of landscape image asset resource names (1200x628).
    square_marketing_images: List of square image asset resource names (1200x1200).
    logo_images: List of logo asset resource names.
    business_name: Business name (max 25 chars).
    final_urls: Landing page URLs.
    call_to_action_text: Optional CTA text.
    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>",
      "long_headline": "<long_headline>",
      "descriptions": "<descriptions>",
      "marketing_images": "<marketing_images>",
      "square_marketing_images": "<square_marketing_images>",
      "logo_images": "<logo_images>",
      "business_name": "<business_name>",
      "final_urls": "<final_urls>"
    },
    "name": "create_responsive_display_ad"
  }
}

Input Schema

Name	Required	Default
`status`	No	ENABLED
`confirm`	No
`headlines`	Yes
`final_urls`	Yes
`ad_group_id`	Yes
`customer_id`	Yes
`logo_images`	Yes
`descriptions`	Yes
`business_name`	Yes
`long_headline`	Yes
`marketing_images`	Yes
`call_to_action_text`	No
`square_marketing_images`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 11, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Beyond annotations, the description discloses the critical two-step safety behavior: an ENABLED ad returns a preview first and requires confirm=True, while a PAUSED ad is created immediately. This is highly useful context for a non-idempotent creation tool, though it does not discuss permissions or rate limits.

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 front-loaded with purpose and safety behavior, then proceeds through a well-organized argument list. Every line earns its place, especially given the complete lack of schema parameter descriptions.

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 13-parameter mutation tool with no output schema, the description covers all required inputs, constraints, defaults, and the crucial preview/confirm workflow. An agent has enough information to call the tool correctly without consulting additional documentation.

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 must compensate and it does: it documents all 13 parameters, including array length limits, character limits, image dimensions, status default, and the interactive confirm parameter. This adds substantial meaning beyond the bare input schema.

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 verb and resource: 'Create a Responsive Display Ad for Display campaigns.' This clearly distinguishes it from sibling tools like create_responsive_search_ad, create_video_ad, and create_demand_gen_ad.

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?

It provides clear context that the ad group must be in a Display campaign and explains the ENABLED vs PAUSED creation flow. It does not explicitly compare against sibling ad-creation alternatives, but the intended use case is unambiguous.

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

Deploy Server