Growomat

Connect a conversion source

create_conversion_source

Connect a revenue/conversion source to the active Space so it feeds measured conversions back to your connected ad platforms. Pass body as { type: 'stripe'|'webhook'|'hubspot'|'salesforce'|'ga4', config?: {...}, accountRef? }. Idempotent per type by default. 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
`body`	Yes	Source payload — { type, config?, accountRef? }.
`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).

TDQS

A4.5/5.0

Behavior4/5

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

Beyond the readOnlyHint=false annotation, the description reveals idempotency per type by default and the scoping behavior, adding meaningful behavioral context. It does not mention auth or rate limits, but the disclosed traits materially help an agent predict behavior.

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 with no fluff: the first states purpose, the second prescribes the body shape, and the third covers idempotency and scoping. Each sentence carries essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the moderate complexity (nested body, space scoping, idempotency), the description covers the main behavioral and payload aspects. It lacks explicit error/response details, but the absence of an output schema makes that less critical. Overall, it is sufficient for correct invocation.

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?

The schema provides basic field descriptions, but the tool description goes further by enumerating the concrete type values (stripe|webhook|hubspot|salesforce|ga4), clarifying config/accountRef as optional, and explaining the space_id override semantics. This substantially augments the schema information.

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 action 'Connect a revenue/conversion source to the active Space' and explains its purpose (feeds measured conversions back to ad platforms). This distinguishes it from sibling tools like create_conversion_action, which target conversion actions rather than sources.

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 scoping: it mentions the active Space, the set_active_space sibling tool for switching, and the space_id override for one call. However, it does not explicitly list alternative tools or when-not-to-use conditions, so it lacks explicit exclusions.

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?