Growomat

Set budget

set_budget

Set the account budget amount/period and arm or disarm the account-level Emergency Brake. The Emergency Brake is ON by default: when real month-to-date spend passes the budget, Growomat automatically pauses the affected campaigns and notifies the owner. Pass emergency_brake=false to disarm it (spending past the budget will then pause nothing). Raising global_budget re-arms a previously-spent brake for the rest of the month. Writes real configuration that can stop live campaigns — confirm intent before disarming.

Input Schema

TableJSON Schema

Name	Required	Description
`period`	No	Whether global_budget is a daily or monthly amount. Monthly is the default the product uses.
`currency`	No	ISO 4217 currency code, e.g. EUR.
`global_budget`	No	Budget amount, interpreted per `period`. Positive.
`emergency_brake`	No	Arm (true) or disarm (false) the account-level Emergency Brake. Default is armed.
`alert_threshold_percent`	No	Percent of budget (50-100) at which the approaching-the-limit warning fires. Default 90.

TDQS

A4.7/5.0

Behavior5/5

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

The description goes far beyond the annotations by explaining the Emergency Brake's automatic campaign-pausing behavior, the re-arming effect of raising global_budget, and the explicit warning that it writes real configuration that can stop live campaigns. This provides rich behavioral context not present in the readOnlyHint/destructiveHint flags.

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 five sentences, each carrying essential information: the core action, the default brake state, the disarm behavior, the re-arming nuance, and a safety warning. No filler or repetition, and the structure is logical.

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?

Despite lacking an output schema and having minimal annotations, the description covers the tool's key behaviors, side effects, and a critical warning. It addresses the five parameters indirectly through context and provides enough information for an agent to use the tool safely and correctly.

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?

With 100% schema coverage, the baseline is 3, but the description adds meaningful behavioral details for emergency_brake (default armed, consequence of disarming) and global_budget (raising it re-arms a spent brake). These insights go beyond the parameter descriptions in the schema, justifying a higher score.

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 explicitly states the tool's function: setting the account budget amount/period and arming/disarming the Emergency Brake. This clearly distinguishes it from siblings like get_budget and release_brake by naming the specific resources and actions.

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

Usage Guidelines4/5

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

The description provides clear context on when to use the tool, such as the Emergency Brake default state and the effect of passing emergency_brake=false. However, it does not explicitly mention alternatives like release_brake or when not to use this tool, so it lacks exclusionary guidance.

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

All Growomat tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation4/5

Most tools follow a clear resource+action pattern (get_ad, update_ad, delete_ad), so entity-level tools are easy to distinguish. The main ambiguity is among reporting/status tools like get_conversion_status, get_conversion_health, get_conversion_report, and account_summary vs. get_performance_stats, which could tempt misselection without reading descriptions.

Naming Consistency5/5

Naming is highly consistent: nearly every resource has create_/get_/update_/delete_/list_ variants, with predictable special verbs like set_, trigger_, preview_, and upload_. Minor exceptions like account_summary or get_angle_readout still follow the same readable verb-driven style.

Tool Count1/5

83 tools is an extreme surface for an MCP server, even one covering ad management. Most entities have full CRUD plus many custom readouts and report variants, which creates context bloat and makes tool selection unnecessarily expensive for the agent.

Completeness4/5

The platform covers the full campaign lifecycle: campaigns, ad groups, ads, keywords, assets, business/creative planes, conversion actions, sync, budget, and targeting are all represented. Minor gaps exist—conversion sources have create/list but no get/update/delete, and there is no explicit way to update or remove a conversion source—but these can be worked around.

Resources

Need Help?