Growomat

Account summary

account_summary

Read-only

Return a single JSON document summarising the account: token info (including token.scheduling.timezones — the per-platform account timezone that ad schedules are interpreted in), visible Spaces, campaign list, per-resource counts, 30-day stats, and the most recent sync (last_sync) so you can tell whether the campaigns are actually live. Backed by parallel SDK calls — the cheapest way to ask 'what's going on with my account?' before deciding what else to do. The counts, campaigns/stats, and last_sync branches are Space-scoped; pass space_id to summarise a non-active Space without changing the session binding. 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

Name	Required	Description	Default
`space_id`	No	Override 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.

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses that it is backed by parallel SDK calls, clarifies the meaning of token.scheduling.timezones, and explains how last_sync indicates whether campaigns are live. It also states the Space-scoping behavior and the override semantics, adding significant context.

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?

The description is front-loaded with the core purpose, followed by details on output components and Space scoping. It is somewhat longer than strictly necessary, but each sentence adds essential context, so it remains efficient and well-structured.

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?

Given no output schema, the description enumerates the key sections of the returned document (token info, Spaces, campaigns, counts, stats, last_sync) and explains the scoping behavior. This makes it sufficiently complete for understanding the tool's output and usage without needing external references.

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?

The single parameter space_id is already fully described in the schema with 100% coverage, including its purpose, default behavior, and effect on session binding. The tool description reinforces this but does not add new meaning beyond the schema, so the baseline 3 is appropriate.

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 returns a single JSON account summary with specific components (token info, Spaces, campaigns, counts, stats, last_sync). It gives the tool a distinct purpose among siblings, emphasizing it as the cheapest way to get an account overview.

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?

Explicitly recommends using this before deciding what else to do, framing it as a discovery/overview tool. It also provides clear guidance on Space scoping: how to switch via set_active_space or override with space_id, and notes that branches are Space-scoped.

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?