Skip to main content
Glama

ads_get_budget_usage

Read-only

READ-ONLY, LIVE. Quanto del budget GIORNALIERO ogni campagna ha già consumato OGGI, in percentuale (dato INTRAGIORNALIERO, aggiornato da Amazon ogni ~10-15 min). Serve alla domanda "quali campagne stanno per restare senza budget adesso / sono già andate dark?": a 100% la campagna esce dall'asta fino a mezzanotte. È l'UNICA fonte del dato di oggi — il data-hub (fact_campaign_daily) è giornaliero e al massimo dice che IERI una campagna ha saturato. Per storico, ACoS, spesa e trend usa execute_sql, NON questo tool. Senza campaign_ids controlla tutte le campagne ENABLED dell'ad product. ad_product: SP (default) | SB | SD.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ads_get_budget_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.
ad_productNoTipo di campagne da controllare (default SP)
profile_idNoAmazon Ads profile id (stringa numerica, da ads_list_profiles). Omesso: profilo predefinito dell'outpost.
campaign_idsNoCampagne specifiche; se omesso controlla tutte le ENABLED
max_campaignsNoTetto di campagne da controllare in auto-discovery (default 300)
threshold_percentNoSoglia per la lista at_risk (default 80)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / profile_id / description
      Added value: +"Amazon Ads profile id (stringa numerica, da ads_list_profiles). Omesso: profilo predefinito dell'outpost."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint/destructiveHint false), it discloses data freshness (~10-15 min Amazon refresh), the operational consequence of hitting 100% (campaign leaves the auction until midnight), and the auto-discovery behavior with its campaign cap. This is meaningful behavioral context an agent could not infer from the structured fields.

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 the key qualifier (READ-ONLY, LIVE) and organized around what it returns, when to use it, and when not to. It is dense and mostly earns its space, though the ad_product enumeration at the end partially repeats the schema enum.

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?

With no output schema, the description carries the return-value burden and does describe the percentage-per-campaign figure and its live nature. It stops short of describing the at_risk list that threshold_percent implies, which leaves one output element unexplained.

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 the baseline is 3; the description adds the interaction semantics that omitting campaign_ids triggers auto-discovery across all ENABLED campaigns of the given ad_product, which the schema alone does not spell out. It does not, however, explain threshold_percent's downstream effect on the at_risk list.

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 states a precise verb+resource+granularity: the percentage of DAILY budget each campaign has already consumed TODAY, refreshed intraday by Amazon. It explicitly distinguishes itself from the data-hub (fact_campaign_daily) and from execute_sql, so an agent can identify it without opening the schema.

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?

It names the exact question the tool answers ('which campaigns are about to run out of budget now / are already dark') and gives an explicit exclusion: for history, ACoS, spend and trends use execute_sql, NOT this tool. It also states the default scope when campaign_ids is omitted (all ENABLED campaigns of the ad product).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources