Skip to main content
Glama
Grona MCP

Grona MCP

by gbasilveira

Create campaign

grona_create_campaign

Create a paused campaign with variations and 15-minute editor links, using an externalId to prevent duplicates; requires an Embed snippet and page variable, and never publishes.

Instructions

Create a paused campaign and variations with 15-minute editor links. Use externalId for duplicate protection. Requires Embed snippet and page variable. Creation never publishes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "url": "<url>",
      "segmentId": "<segmentId>",
      "segmentValue": "<segmentValue>"
    },
    "name": "grona_create_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http(s) page URL.
listNo
nameYes
slugNo
typeNo
conditionNo
segmentIdYesCustom window variable name, up to 128 characters.
externalIdNoUnique campaign identifier in your workspace; optional on create.
segmentValueYesExact page-variable string match.
trafficSplitNo
pageTargetingNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses important behavior: the campaign is created paused, editor links expire after 15 minutes, prerequisites are required, and creation never publishes. These details materially help an agent understand the mutation's effect, though permissions, failure modes, and what "variations" includes are not covered.

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 four short sentences with no wasted wording. The most important constraints are front-loaded: paused creation, editor-link expiry, duplicate protection, prerequisites, and the no-publish guarantee.

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

Completeness2/5

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

This is a complex 11-parameter creation tool with nested trafficSplit data and low schema description coverage. Although an output schema and annotations help, the description does not explain most parameters or the alternative creation sibling, leaving significant gaps for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 36% across 11 parameters, so the description needs to compensate. It adds meaning for externalId and references the page-variable requirement, but it leaves most parameters, including list, slug, type, condition, trafficSplit, and pageTargeting, unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: "Create a paused campaign and variations." It is clear what the tool does, but it does not explicitly differentiate itself from the sibling grona_create_campaign_once, which is likely the key alternative for campaign creation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives some usage guidance: use externalId for duplicate protection and prerequisites include an Embed snippet and page variable. However, it does not say when to use this tool versus grona_create_campaign_once or other campaign-creation siblings, so the routing guidance remains implied.

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