Google Ads MCP Server

create_smart_campaign

Automate the creation of a Smart campaign in Google Ads by specifying customer ID, campaign name, daily budget, and business name.

Instructions

Create a Smart campaign

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>",
      "name": "<name>",
      "budgetAmountMicros": "<budgetAmountMicros>",
      "businessName": "<businessName>"
    },
    "name": "create_smart_campaign"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Campaign name
`finalUrl`	No	Website URL
`customerId`	Yes	Google Ads customer ID
`businessName`	Yes	Business name
`budgetAmountMicros`	Yes	Daily budget in micros

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

D1.9/5.0

Behavior1/5

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

With no annotations provided, the description must disclose behavioral traits but does not. It does not mention that this is a create operation with side effects, required permissions, validation behavior, or post-creation steps. This is a serious omission for a mutation tool.

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

Conciseness2/5

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

The description is a single short sentence, but it is under-specified rather than concise. It does not earn its place because it restates the tool name without adding informative content.

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

Completeness1/5

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

Given the tool's complexity as a Smart campaign creation tool with 5 parameters and many sibling campaign types, this description is completely inadequate. It provides zero context about the campaign type, required setup, or expected behavior, leaving an agent without enough information to make an informed invocation.

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 has 100% coverage with descriptions for all 5 parameters, so the baseline is 3. The description adds no parameter-specific semantics beyond what the schema already provides; it simply names the tool's purpose without elaboration.

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

Purpose2/5

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

The description 'Create a Smart campaign' is a tautology that merely restates the tool name. It provides no information about what a Smart campaign is or how it differs from sibling tools like create_performance_max_campaign or create_demand_gen_campaign.

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

Usage Guidelines2/5

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

No usage guidance is provided. The description does not mention when to use Smart campaigns versus other campaign creation tools, nor any prerequisites or context. This is a clear gap given the many sibling campaign creation tools.

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

Deploy Server