Skip to main content
Glama
johnoconnor0

Google Ads MCP Server

by johnoconnor0

google_ads_add_location_extension

Add a location extension to Google Ads campaigns to show your business address, phone number, and map marker, helping customers find your physical locations and increase foot traffic.

Instructions

Add a location extension to display your business address in ads.

Location extensions show your business address, phone number, and a map marker with your ads. They help customers find your physical business locations and increase foot traffic to your stores.

Args: customer_id: Google Ads customer ID (10 digits, no hyphens) campaign_id: Campaign ID to add location extension business_name: Business name (up to 80 characters) address_line_1: Street address city: City name province: State/province code (e.g., "CA", "NY", "TX") postal_code: ZIP or postal code country_code: 2-letter country code (e.g., "US", "GB", "CA") phone_number: Optional phone with country code (e.g., "+1-555-123-4567")

Returns: Location extension creation result

Example: google_ads_add_location_extension( customer_id="1234567890", campaign_id="12345678", business_name="Acme Coffee Shop", address_line_1="123 Main Street", city="San Francisco", province="CA", postal_code="94102", country_code="US", phone_number="+1-415-555-1234" )

Benefits: - Show your address and location on a map - Increase foot traffic to physical locations - Make it easy for customers to find you - Add phone numbers for direct calls - Improve local search visibility

Requirements: - Location extensions require address verification - Best practice: Link with Google My Business - Phone numbers should include country code - All address fields must be valid

Note: For advanced location management, use Google My Business integration with Local campaigns for automatic location syncing and store visit tracking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idYes
campaign_idYes
business_nameYes
address_line_1Yes
cityYes
provinceYes
postal_codeYes
country_codeYes
phone_numberNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description bears full responsibility. It describes the effect (show address, phone, map marker) and mentions requirements and optional phone, but lacks details on idempotency, error handling, or permission needs.

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 sections (Args, Example, Benefits, etc.) and front-loaded with purpose. However, it is somewhat lengthy with some repetition, such as benefits reiterating earlier points.

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?

Given the 9 parameters and no schema descriptions, the description thoroughly covers all inputs, includes an example, and provides usage context and requirements. The output schema exists but is not shown; the description explains the return value sufficiently.

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 coverage is 0%, but the description provides detailed parameter explanations (format, length, examples) for all 9 parameters, fully compensating for the missing schema 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 clearly states 'Add a location extension to display your business address in ads' and explains what location extensions do. It effectively distinguishes from sibling extension tools by focusing on address display, a unique purpose.

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 provides requirements (address verification, GMB linking, valid fields) and a note on advanced management, but does not explicitly compare with other extension tools or state when not to use this tool.

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