Skip to main content
Glama
johnoconnor0

Google Ads MCP Server

by johnoconnor0

google_ads_app_performance

Retrieve key performance indicators for App campaigns, including impressions, clicks, conversions, and cost data, with optional date range filtering.

Instructions

Get performance metrics for App campaigns.

Retrieves key performance indicators for app campaigns including impressions, clicks, conversions (installs), and cost data.

Args: customer_id: Google Ads customer ID (10 digits, no hyphens) campaign_id: Optional campaign ID to filter (returns all if not specified) date_range: Date range - LAST_7_DAYS, LAST_30_DAYS, LAST_90_DAYS, etc.

Returns: Dictionary with app campaign performance data including: - campaigns: List of campaign metrics - total_campaigns: Number of app campaigns

Example: Get performance for all app campaigns in the last 30 days: google_ads_app_performance( customer_id="1234567890", date_range="LAST_30_DAYS" )

Metrics Included: - Impressions: Ad views across all networks - Clicks: User clicks - CTR: Click-through rate - Cost: Total spend - Conversions: App installs or in-app actions - Conversion Value: Value of conversions - Cost per Conversion: Average cost for each conversion

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idYes
campaign_idNo
date_rangeNoLAST_30_DAYS

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden. Describes the operation as retrieving metrics, implying a read-only, non-destructive action. Lists specific metrics returned, but does not mention rate limits, authentication needs, or data freshness. Overall satisfactory but lacks some depth.

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?

Well-structured with headers for description, args, returns, example, and metrics. Content is relevant and front-loaded. Slightly verbose due to example and metrics list, but still concise overall.

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 tool has an output schema (true) and only three parameters, the description is complete. Covers all parameter details, return structure, and examples, providing sufficient context for an agent to use the tool correctly.

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%, so description fully compensates by explaining each parameter: customer_id format, campaign_id as optional filter, date_range with enum examples. Also describes return structure and lists metrics, adding significant meaning beyond the bare 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?

Explicitly states 'Get performance metrics for App campaigns', using a specific verb and resource. Distinguishes from sibling tools like google_ads_campaign_performance and google_ads_app_conversions by focusing on app campaign metrics.

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?

Provides example usage and explains optional parameters, but does not explicitly state when to use this tool versus alternatives such as google_ads_campaign_performance or google_ads_app_conversions. No exclusion criteria or context for when not to use.

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