Skip to main content
Glama

Propose an ad budget change

update_ad_budget

Propose a budget change (max ±30% per call, reason required). It becomes an approval item — it never changes the budget silently.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "campaign_id": "<campaign_id>",
      "daily_budget": "<daily_budget>",
      "reason": "<reason>"
    },
    "name": "update_ad_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYes
campaign_idYes
daily_budgetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Goes well beyond the annotations (readOnly=false, destructive=false, idempotent=false) by disclosing that the call creates a pending approval item rather than applying the change immediately, plus a ±30% per-call limit and a mandatory reason. It stops short of describing what the approval item looks like or whether repeat proposals stack.

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?

Two tight sentences with the key constraint and the approval behavior front-loaded; no filler. The parenthetical packs three facts efficiently, though slight restructuring could make the cap apply more clearly to daily_budget.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-required-parameter mutation with no output schema, the description covers the approval workflow and one validation rule, which is the most important behavior. It leaves the parameters themselves unexplained, which is the main completeness gap.

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

Parameters2/5

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

Schema description coverage is 0% for all three required parameters, so the description must compensate and largely does not. It adds only the ±30% cap, and even that is ambiguous about whether daily_budget is a new absolute value or a delta, and says nothing about campaign_id format or currency.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (propose) and resource (budget change) for ad campaigns, and the title reinforces it. It is clearly distinguished from a silent mutation, though no sibling tool is named as an alternative.

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?

The ±30% per-call cap implicitly tells the agent large changes need multiple calls, and 'reason required' signals the justification expectation. However, there is no explicit when-to-use vs. when-not guidance and no named alternative for budget changes exceeding the cap.

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