Skip to main content
Glama
Grona MCP

Grona MCP

by gbasilveira

Create campaign once

grona_create_campaign_once

Create a campaign once with an external ID; on conflict, compare the existing campaign identity and return fresh editor links without patching or publishing the existing campaign.

Instructions

Require externalId; on 409 fetch and compare existing campaign identity before recovering with fresh editor links. Conflict never patches or publishes an existing campaign.

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": {
      "campaign": "<campaign>"
    },
    "name": "grona_create_campaign_once"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is known; the description then adds genuinely new behavior: 409 conflict triggers a fetch-and-compare of existing campaign identity, recovery returns fresh editor links, and conflicts never patch or publish. That conflict-handling and no-mutation-on-conflict contract is exactly the kind of context annotations can't express. It stops short of describing auth needs or rate limits.

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

Conciseness3/5

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

Two sentences with no filler, but the opening is a mid-thought parameter constraint ('Require externalId') rather than a front-loaded statement of what the tool creates. The second sentence is dense and precise. It is short but not structured around the agent's primary need: identifying the operation.

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

Completeness3/5

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

An output schema exists, so return values needn't be explained, and annotations cover the safety profile. However, for a create tool wrapping a large nested campaign object (with trafficSplit, pageTargeting, condition, type enums), the description leaves the payload almost entirely unexplained and never resolves the externalId required/optional discrepancy. It is complete on the conflict path but thin on the input contract.

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 0% at the top level, though nested properties like externalId and segmentId carry their own descriptions. The description's 'Require externalId' adds critical meaning — but it directly conflicts with the schema, which describes externalId as 'optional on create', so the agent is left to reconcile two contradictory statements. None of the other nested campaign fields are addressed.

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

Purpose3/5

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

The description never states plainly that this tool creates a campaign; the verb+resource must be inferred from the name and title. What it does state is a specific behavioral contract (externalId required, 409 handling, no patching or publishing on conflict), which implies a create-once operation but doesn't name it. It never mentions the sibling grona_create_campaign to differentiate the 'once' variant.

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?

'Require externalId' functions as an entry precondition, and the 409 recovery path tells the agent what to do on conflict, so usage is implied rather than stated outright. There is no explicit 'use this instead of grona_create_campaign when...' routing, and no statement of when not to use it. The single prerequisite is useful but the alternative-selection guidance is absent.

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