Skip to main content
Glama
Grona MCP

Grona MCP

by gbasilveira

Set campaign status

grona_set_campaign_status
Destructive

Set a Grona campaign to live or paused, applying the status to real visitors after propagation. Use this direct route when no launch readiness checks are needed.

Instructions

Set live or paused. live affects real visitors after propagation. Prefer grona_launch_campaign for readiness guards; this direct route has none.

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": {
      "campaignId": "<campaignId>",
      "status": "<status>"
    },
    "name": "grona_set_campaign_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYes
campaignIdYesOpaque Grona campaign id or externalId.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructive=true, openWorldHint=true and idempotentHint=false, so the safety profile is known. The description adds real context beyond that: 'live' affects real visitors and only after propagation, and this route skips readiness guards entirely. It does not state reversibility (that paused undoes live) or permission requirements, which keeps it at 4.

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 short sentences, each carrying distinct information: state values, side effect, and sibling routing. The risk-relevant content is front-loaded with zero 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?

For a 2-parameter mutation with an output schema and full annotations, the description covers the key risk (real traffic, propagation delay, absent guards). Minor gaps remain around reversibility and what happens to in-flight visitors when pausing, but nothing needed to call it correctly is missing.

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 50%: campaignId is documented in the schema but the status enum carries no field description. The description compensates by explaining what 'live' actually means in effect (real visitor traffic after propagation), adding meaning beyond the bare enum values, though 'paused' is left 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?

States a specific verb and the two-state value set ('Set live or paused') for the campaign status resource named in the title, and explicitly contrasts itself with grona_launch_campaign. It stops short of naming the resource in the sentence itself, relying on the tool name, which keeps it just under a 5.

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 routes the agent: prefer grona_launch_campaign for readiness guards, and warns this direct route has none. That gives a clear when-to-prefer-the-alternative rule, though it leaves implicit the exact condition under which this direct route is the right choice (e.g. campaign already validated).

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