Skip to main content
Glama

google_ads_budget_reallocation

Proposes budget reallocation for Google Ads: cuts up to 20% from inefficient campaigns and distributes equally to efficient ones. Returns plan without applying changes.

Instructions

Propose a budget reallocation plan by cutting up to 20% from INEFFICIENT campaigns and distributing the freed amount equally across EFFICIENT campaigns. Returns the full google_ads_budget_efficiency payload plus {reallocation_plan:[{campaign_id, campaign_name, action ('DECREASE'|'INCREASE'), current_daily_budget, proposed_daily_budget, change_amount, reason}], total_freed, summary}. When the account has no campaigns with spend in the window, the response short-circuits to just {...efficiency payload, reallocation_plan:[], summary:'No campaigns with spend in period'} and the total_freed key is omitted — parse defensively. Reductions below 100 (currency units) are skipped. Current daily budgets are fetched via get_budget — failures fall back to 0. Read-only — emits a plan only, does not apply any budget changes. To actually apply a change use google_ads_budget_update; for the efficiency scoring alone use google_ads_budget_efficiency.

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?

No annotations provided, but description discloses all key behaviors: return payload structure, short-circuit when no campaigns with spend, skipping reductions below 100, fallback to 0 for budget failures, and explicit read-only nature. Leaves no behavioral mystery.

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?

Front-loaded with main purpose, but slightly long. Every sentence adds value; could be trimmed slightly but still well-structured.

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?

No output schema, but description details the full return structure including reallocation_plan fields, total_freed, summary, and edge cases (short-circuit, missing key). Also mentions failure handling. Complete and self-sufficient.

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?

Both parameters have schema descriptions (100% coverage). Description adds value: customer_id explains fallback to credentials; period provides usage guidance beyond enum values (e.g., 'use LAST_7_DAYS for recent changes').

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?

Clearly states it proposes a budget reallocation plan with specific logic (cut up to 20% from inefficient campaigns, distribute equally to efficient). Distinguishes from siblings: google_ads_budget_efficiency (scoring only) and google_ads_budget_update (applying changes).

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?

Explicitly tells when to use this vs alternatives: 'To actually apply a change use google_ads_budget_update; for the efficiency scoring alone use google_ads_budget_efficiency.' Also guides period selection with examples (shorter window for recent changes, longer for trends).

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