Growomat

Set ad schedule

set_ad_schedule

Set a campaign's weekly ad schedule with friendly input and correct, platform-aware timezone handling — the easy front door over update_campaign's adSchedule. Pass HH:MM times, day shorthands (MON…SUN, WEEKDAYS, WEEKEND) and/or a preset. Windows may cross midnight (19:00->07:00) and are auto-split. timezone:'local' uses the searcher's local time on Microsoft (AdScheduleUseSearcherTimeZone); Google cannot localize per searcher, so pass an explicit IANA zone (e.g. 'Europe/Istanbul') to offset-bake the hours to that location relative to the account timezone. Use dry_run:true to preview the exact expanded schedule and any warnings WITHOUT mutating the campaign. Scoped to the active Space.

Input Schema

TableJSON Schema

Name	Required	Description
`preset`	No	A named schedule, expanded server-side. May be combined with windows to add to it.
`dry_run`	No	If true, return the expanded schedule + warnings WITHOUT writing. Use to learn the exact result before committing.
`windows`	No	Friendly windows. Each item: { days: ["MON".."SUN" \| "WEEKDAYS" \| "WEEKEND"], start: "HH:MM", end: "HH:MM", bidModifier?: 0.1-10 }. Minutes must be :00/:15/:30/:45. end may be "24:00"; an end at or before start crosses midnight and is auto-split.
`platform`	No	Disambiguate timezone semantics when the campaign is linked to multiple platforms. Optional; inferred from the campaign's platform links otherwise.
`space_id`	No	Override the active Space for this one call.
`timezone`	No	'local' (searcher-local on Microsoft; account-time + warning on Google), 'UTC', or an IANA zone like 'Europe/Rome'. Omit to use the account timezone. Explicit zones that differ from the account zone are offset-baked into the stored hours (with a DST caveat in the response).
`campaign_id`	Yes	Campaign id (as returned by list_campaigns).

TDQS

A4.9/5.0

Behavior5/5

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

The description discloses mutation behavior by noting dry_run:true previews 'WITHOUT mutating the campaign', implying normal calls do mutate. It explains auto-splitting of midnight-crossing windows and offset-baking for explicit timezones, adding behavioral context beyond the readOnlyHint=false annotation.

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?

Though a single dense paragraph, every sentence adds value – no fluff. It could be structured into bullets for scannability, but the flow is logical: purpose, input format, edge cases, timezone, dry-run, scope.

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?

For a complex tool with no output schema, the description covers input formats, timezone semantics, platform differences, mutation safety via dry_run, and scoping. It leaves little ambiguous about expected behavior.

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?

Schema covers 100% of params, and the description amplifies key semantics: timezone explains 'local', 'UTC', IANA zone offset-baking; windows explains HH:MM, day shorthands, midnight split; dry_run role. This adds meaning beyond the schema placeholders.

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 opens with 'Set a campaign's weekly ad schedule' – a clear verb+resource. It explicitly distinguishes from update_campaign by calling itself 'the easy front door over update_campaign's adSchedule', which sets it apart from the main update tool.

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 recommends itself as the preferred path for scheduling ('easy front door over update_campaign's adSchedule'), implicitly guiding away from using update_campaign. It provides context on platform-specific timezone behavior ('Microsoft... Google cannot localize per searcher') and scoping to the active Space.

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?