Growomat

Validate campaign for export

validate_export

Read-only

Pre-flight a campaign before syncing: evaluates it against each connected platform's capability rules with zero platform calls and returns structured findings (blocked / unsupported / degraded / ok). valid: false means at least one platform will REFUSE this campaign — fix the named findings before trigger_sync instead of discovering the refusal in a failed sync. Pass platforms to check specific ones (a named platform is validated even when unconnected).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`platforms`	No	Platform ids to validate against; defaults to every connected platform.
`campaign_id`	Yes	The campaign to validate.

TDQS

A4.7/5.0

Behavior5/5

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

Despite readOnlyHint being present, the description adds significant behavioral detail: zero platform calls, severity levels (blocked/unsupported/degraded/ok), and the meaning of valid:false. It also explains behavior for unconnected platforms, going well beyond annotations.

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?

Three sentences, front-loaded with the core purpose, then consequence, then parameter tip. Every sentence earns its place with no redundancy or filler.

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?

The description covers the tool's purpose, output categories, and actionable outcome (valid:false means refusals). Despite no output schema, it provides enough context for an agent to understand what to expect and why to use it.

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?

Schema coverage is 100%, providing baseline 3. The description adds nuance for the 'platforms' parameter (validated even when unconnected) and reinforces the default behavior, adding value beyond the schema. No new meaning for campaign_id, but the increment is justified.

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 uses a specific verb ('pre-flight') and resource ('campaign') and clearly explains the tool evaluates campaigns against platform capability rules, returning structured findings. This distinguishes it from sibling tools like trigger_sync, which actually performs the sync.

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?

Explicitly states 'before syncing' and instructs to fix findings before trigger_sync, providing clear guidance on when to use the tool. However, it does not explicitly mention alternatives or when not to use it, so slightly short of the strongest 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?