Skip to main content
Glama

campaign_daily_budget_preview

Read-onlyIdempotent

Preview a campaign daily-budget update using typed money before committing changes. Specify the campaign, ad account, and amount with currency to validate the new budget.

Instructions

Preview a campaign daily-budget update with typed money.

Input Schema

NameRequiredDescriptionDefault
amountYes
profileYeslocal Apple Ads profile name
campaignIdYes
adAccountIdYesApple Ads ad account ID

Output Schema

NameRequiredDescriptionDefault
errorNo
previewNo
summaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds 'typed money' to indicate the amount parameter is a structured object, but provides no further behavioral context such as what 'preview' entails (e.g., validation vs. diff) or any prerequisites.

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?

A single efficient sentence that front-loads the action and resource without any wasted words.

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?

Given the presence of an output schema and rich annotations, the description covers the core purpose and the typed money aspect. However, for a preview tool with many siblings, it lacks clarity on what preview means operationally and how it relates to other budget-related preview tools, leaving a gap in contextual understanding.

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

Parameters3/5

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

With 50% schema description coverage, the description adds meaning only for the amount parameter by calling out 'typed money'. It does not compensate for the undocumented campaignId parameter or elaborate on profile/adAccountId beyond their schema snippets.

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?

The description states a specific verb (Preview) and resource (campaign daily-budget update), and 'with typed money' signals the structured amount parameter. It does not explicitly distinguish itself from similar preview tools like campaign_update_preview, so it falls short of a 5.

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

Usage Guidelines2/5

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

No explicit when-to-use or when-not-to-use guidance is given. It does not clarify how this preview differs from campaign_update_preview or daily_budget_recommendation_apply_preview, leaving the agent to infer its role.

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

Deploy Server

Other Tools