Skip to main content
Glama
johnoconnor0

Google Ads MCP Server

by johnoconnor0

google_ads_create_local_campaign

Create a local campaign to drive store visits and foot traffic by promoting physical business locations across Google Search, Maps, Display, and YouTube.

Instructions

Create a Local campaign to drive store visits and foot traffic.

Local campaigns promote physical business locations through Google properties including Search, Maps, Display, and YouTube. They require Google My Business integration and optimize for local actions (store visits, calls, directions).

Args: customer_id: Google Ads customer ID (10 digits, no hyphens) campaign_name: Name for the local campaign budget_amount: Daily budget in account currency location_ids: List of Google My Business location IDs optimization_goal: Optimization goal - "STORE_VISITS" or "STORE_SALES"

Returns: Dictionary with campaign creation results including: - campaign_id: Created campaign ID - campaign_name: Campaign name - resource_name: Full resource name - budget: Daily budget amount - location_count: Number of locations - optimization_goal: Selected optimization goal

Example: Create a local campaign for 3 store locations: google_ads_create_local_campaign( customer_id="1234567890", campaign_name="Summer Store Promotions", budget_amount=50.0, location_ids=["loc_123", "loc_456", "loc_789"], optimization_goal="STORE_VISITS" )

Notes: - Requires Google My Business account linking - Campaigns start in PAUSED status - Store visit data may take 4-6 weeks to accumulate - Automatically optimizes ad placement across Google properties

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idYes
campaign_nameYes
budget_amountYes
location_idsYes
optimization_goalNoSTORE_VISITS

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description effectively discloses behavioral traits: it requires GMB linking, starts campaigns in PAUSED status, notes 4-6 weeks for store visit data accumulation, and mentions automatic placement optimization across Google properties. This adds useful context beyond the schema.

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

Conciseness4/5

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

The description is well-structured with clear sections (purpose, Args, Returns, Example, Notes) and front-loads key information. While informative, it is slightly verbose; however, it efficiently conveys all necessary details without 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?

Given the tool's complexity (5 parameters, creation behavior, and dependencies), the description covers purpose, parameter details (enhanced with format/values), output structure via Returns, and behavioral notes. Omits error handling or permissions beyond GMB linking, but overall sufficiently 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?

The description's Args section adds significant meaning beyond the schema's 0% coverage, detailing format for customer_id (10 digits, no hyphens), daily budget amount, location IDs, and allowed optimization_goal values ('STORE_VISITS' or 'STORE_SALES'). The example further clarifies usage.

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 clearly states 'Create a Local campaign to drive store visits and foot traffic' and explains that it promotes physical business locations. This verb+resource combination distinguishes it from sibling campaign creation tools like create_campaign, create_app_campaign, etc., which target different campaign types.

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 context that local campaigns require Google My Business integration and are for physical stores, but it does not explicitly state when to use this tool versus alternatives or provide when-not guidance. It lacks comparative usage direction among 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.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/johnoconnor0/google-ads-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server