Skip to main content
Glama
Grona MCP

Grona MCP

by gbasilveira

Update campaign

grona_update_campaign
Destructive

Patch mutable campaign fields and return the full campaign; retry only with the immutable Grona id, and ensure traffic split variation ids total 100.

Instructions

Patch mutable fields; returns full campaign. url/type/pageTargeting are fixed at creation. Retry only by immutable Grona id. trafficSplit keys are variation ids totaling 100.

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>",
      "changes": "<changes>"
    },
    "name": "grona_update_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
changesYes
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.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, openWorldHint=true, so the safety profile is covered. The description adds real value beyond that: partial-patch semantics, that the full campaign is returned, that certain fields are immutable, and a retry-safety rule that compensates for the non-idempotent hint. It does not explain what happens to omitted fields or whether a partial failure leaves the campaign in a mixed state, which is significant for a destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short clauses, each carrying a distinct constraint, with the core definition and return shape front-loaded. It is dense but readable; a tiny structural cue (separating the immutability note from the trafficSplit rule) would make it scannable rather than a run-on list.

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?

With an output schema present, the description need not explain return values, and it correctly just says the full campaign is returned. For a destructive, non-idempotent, nested-object patcher it covers immutability, retry, and the trafficSplit invariant, leaving only minor gaps around omitted-field behavior and the campaignId/externalId question.

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 description coverage is 50%, and the description contributes a genuinely non-obvious rule: trafficSplit keys are variation ids and must total 100, which the schema only expresses as per-value 0-100 bounds. It also frames campaignId as an immutable Grona id even though the schema allows an externalId, which narrows the parameter ambiguously. The other nested fields (name, slug, list, status, condition, segmentId, segmentValue) get no treatment beyond what the schema already documents, so it only partially compensates for the coverage gap.

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?

"Patch mutable fields; returns full campaign" gives a specific verb (patch), a scope (mutable fields only), and the return shape, which distinguishes it from create/delete siblings. The resource is only named by the tool name, not in the prose, so it stops just short of 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 Guidelines3/5

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

It states what cannot be changed (url/type/pageTargeting are fixed at creation) and gives retry guidance ("retry only by immutable Grona id"), which is genuine when-to-use context. However it never names or rules out the obvious overlapping siblings grona_set_campaign_status and grona_set_ab_split, even though status and trafficSplit are mutable here, so the agent must infer which tool is appropriate.

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