Skip to main content
Glama

google_ads_budget_efficiency

Evaluate how well your Google Ads budget is allocated by scoring each campaign's cost vs conversion efficiency. Returns efficiency ratios, verdicts, and recommendations to reallocate spending from inefficient to efficient campaigns.

Instructions

Score budget allocation efficiency across every ENABLED Google Ads campaign. Returns {period, total_cost, total_conversions, campaigns:[{campaign_id, name, cost, conversions, cost_share, cv_share, efficiency_ratio (cv_share / cost_share), verdict ('EFFICIENT' when ratio > 1.2, 'INEFFICIENT' when < 0.8, 'NORMAL' otherwise, 'NO_COST' when cost==0), cpa}], recommendations:[strings], insights:[strings]}. Per-campaign cost/conversions come from get_performance_report — individual failures are silently treated as zero. Read-only. For a concrete DECREASE/INCREASE reallocation plan use google_ads_budget_reallocation; to change a single budget use google_ads_budget_update.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idNoGoogle Ads customer ID as a 10-digit string without dashes (e.g. '1234567890'). Optional — falls back to GOOGLE_ADS_CUSTOMER_ID / GOOGLE_ADS_LOGIN_CUSTOMER_ID from the configured credentials when omitted.
periodNoReporting window for the metrics. Default 'LAST_30_DAYS'. Use a shorter window (LAST_7_DAYS / LAST_14_DAYS) when diagnosing recent changes; use LAST_90_DAYS for trend baselines.
Behavior5/5

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

Despite no annotations, the description fully discloses behavioral traits: it is read-only, uses get_performance_report data, silently treats individual failures as zero, and details the return structure including verdict logic. This compensates for the missing annotations.

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 well-structured and front-loaded with purpose, followed by return details, behavioral notes, and alternatives. Every sentence contributes valuable information without redundancy.

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?

With no output schema, the description compensates by fully detailing the return structure and including behavioral notes. It covers the scope (ENABLED campaigns), failure handling, and read-only nature, leaving no critical gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by providing usage advice for the period parameter (e.g., shorter windows for diagnosing recent changes, LAST_90_DAYS for trends), which goes beyond 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 the tool scores budget allocation efficiency across all ENABLED Google Ads campaigns, using specific verbs and resources. It distinguishes itself from sibling tools like google_ads_budget_reallocation and google_ads_budget_update, making its purpose unambiguous.

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

Usage Guidelines5/5

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

The description explicitly advises when to use this tool versus alternatives: for a concrete reallocation plan use google_ads_budget_reallocation, and for single budget changes use google_ads_budget_update. It also notes the tool treats individual failures as zero, providing context for interpreting results.

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/logly/mureo'

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