Skip to main content
Glama
Grona MCP

Grona MCP

by gbasilveira

Launch reviewed campaign

grona_launch_campaign
Destructive

Launches a campaign by requiring edit and preview attestations, verifying the live page by immutable ID, and blocking missing snippets or unusable variations.

Instructions

Require edited=true and previewed=true attestations, freshly verify actual campaign page, then set live by immutable id. Refuse absent snippet/unusable variations. Direct tools remain unguarded.

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>",
      "edited": "<edited>",
      "previewed": "<previewed>"
    },
    "name": "grona_launch_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
editedYesAttest saved edits have been reviewed.
previewedYesAttest every intended variation has been previewed.
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

A3.8/5.0
Behavior4/5

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

Goes meaningfully past the annotations: it discloses that the tool re-verifies the live campaign page, refuses when a snippet is absent or variations are unusable, and requires two explicit human attestations before mutating. That is real guardrail behavior an agent could not infer from destructiveHint/openWorldHint alone; what remains unexplained is the failure response shape, though an output schema exists.

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, precondition first, action second, refusal conditions third, with no filler. The telegraphic style is dense but each clause carries distinct operational 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?

For a destructive, open-world mutation with an output schema, the description covers preconditions, the verification step, refusal cases, and the identity key used for targeting. It is slightly short on what 'freshly verify' entails operationally (remote fetch, latency, what happens on verification failure), which is the only notable gap.

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?

Schema coverage is 100%, so the schema already documents all three parameters, including the const-true attestations and the opaque campaign id. The description reinforces intent ('attestations', 'immutable id') but adds no format, sourcing, or validation detail beyond the schema.

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 effect ('set live by immutable id') on the named resource (campaign), so an agent can tell this is the guarded launch action rather than a generic status change. It does not explicitly contrast with grona_set_campaign_status or grona_create_campaign, so sibling differentiation is only partially inferable.

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?

Usage is implied through prerequisites: both attestations must be true and the page must be freshly verified first. The closing line 'Direct tools remain unguarded' hints that unnamed alternatives skip the guardrails, but it never names an alternative or states a when-not-to-use condition explicitly.

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