Growomat

Create angle

create_angle

Create an angle — a claim a set of ads argues, scoped to one business. angleType must be a registry id from get_creative_vocabulary. 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	Request body matching the AngleCreate schema.
`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.4/5.0

Behavior4/5

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

The description adds meaningful non-obvious behavior by explaining that the operation is scoped to the active Space and can be overridden with space_id. It also explains that angleType is not arbitrary but a registry id from a vocabulary tool, which goes beyond the 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?

The description is compact and front-loaded: purpose, vocabulary requirement, and Space-scoping behavior are all stated in three efficient sentences with no filler.

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?

An agent gets enough to construct a valid request: the business scoping, the angleType source, and the Space-handling semantics. A small gap is not saying what happens on invalid or duplicate data, but that is not essential for basic invocation.

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?

The schema includes both top-level parameters, but the description adds real semantics for body.angleType — it must come from get_creative_vocabulary. It also clarifies businessId as the business scope and reinforces the meaning of space_id.

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 defines a specific verb and resource — create an angle — and explains what an angle is: 'a claim a set of ads argues, scoped to one business.' This distinguishes it from other create_* tools like create_concept or create_asset.

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?

It provides clear prerequisites and setup context: angleType must come from a registry via get_creative_vocabulary, and the call is scoped to the active Space. It does not explicitly list when not to use this tool, but the definition is specific enough for basic selection.

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?