Skip to main content
Glama

Growomat

by com.growomat

Trigger sync

trigger_sync
Destructive

Push the active Space's campaigns to your connected ad platforms and import remote changes. ASYNCHRONOUS: returns a syncId immediately with status 'started' (or 'nothing_to_sync'); the sync runs in the background. Poll get_sync_status with the syncId until its status is terminal (completed, partial, failed, or cancelled). Spends real ad budget and mutates external platforms. The platform connection is account-wide; the campaigns synced are the active Space's. Fails if a sync is already running in this Space. Scoped to the active Space — see set_active_space to switch, or pass space_id to override for this one call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNoRe-export in-scope campaigns even when nothing changed — re-runs the full tree + targeting/extensions/labels. Use to repair campaigns synced before a fix. For campaigns deleted in the ad platform, unlink_campaigns then sync.
optionsNoPer-entity toggles: includeAdGroups, includeKeywords, includeAds (all default true).
space_idNoOverride the active Space for this one call. Defaults to the active Space set via set_active_space (or GROWOMAT_SPACE_ID on the server). Pass to read/write a different Space without changing the session binding.
plan_hashNoBind execution to a plan you previewed: pass the planHash from preview_sync_plan and the sync runs only if the recomputed plan still matches (else SYNC_PLAN_DRIFT). Makes 'preview then sync' a real safety gate.
platformsNoPlatform ids to sync, e.g. ["google-ads"]. Omit for all connected.
campaign_idsNoHARD scope: sync ONLY these campaigns, on every platform and phase (import/export/remove). Never silently widened — a plan that would touch a campaign outside this set is rejected (SYNC_SCOPE_EXCEEDED) unless confirm_full_space is set. Omit to plan the whole Space. Pair with preview_sync_plan to see the exact set first.
confirm_full_spaceNoAcknowledge a large blast radius. Required when an unscoped whole-Space sync would mutate more than 10 campaigns, or to override SYNC_SCOPE_EXCEEDED. Guards against a one-campaign request silently escalating to the whole Space.

TDQS

A4.7/5.0
Behavior5/5

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

The description goes well beyond the annotations (destructiveHint=true) by stating it 'Spends real ad budget and mutates external platforms,' explaining the asynchronous flow with immediate syncId and status values, and noting that it fails if another sync is running. These are critical behavioral details not captured by 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but well-structured: it front-loads the primary action, then async behavior, side effects, failure mode, and scope overrides. Each sentence adds unique value, and it remains concise relative to the tool's complexity.

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 having no output schema, the description fully explains the return contract (syncId with status 'started' or 'nothing_to_sync'), the polling workflow including terminal statuses, the destructive side effects, and the scope semantics. This is sufficient for an agent to use the tool correctly, especially with rich sibling context.

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?

Schema description coverage is 100%, so the baseline is 3. The main description adds some context about space_id overriding the active Space, but the input schema already provides comprehensive per-parameter descriptions, including examples and caveats. No additional meaning is needed beyond the schema.

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 clearly states the tool's function: 'Push the active Space's campaigns to your connected ad platforms and import remote changes.' It uses specific verbs and identifies the resource, and the async behavior distinguishes it from siblings like cancel_sync and preview_sync_plan.

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 explicitly tells when to use the tool (to sync campaigns), when not to (fails if a sync is already running), and provides alternatives such as 'see set_active_space to switch' and 'pass space_id to override.' It also references get_sync_status for polling, giving clear operational guidance.

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

All Growomat toolsInspect
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