Skip to main content
Glama
Grona MCP

Grona MCP

by gbasilveira

Delete campaign

grona_delete_campaign
Destructive

Permanently deletes a campaign and its unshared variations, freeing the external ID for reuse. Retry with the immutable Grona ID; visitor updates propagate asynchronously.

Instructions

Permanently delete campaign and unshared variations. Frees externalId for reuse. Retry only by immutable Grona id. Propagation to visitors is asynchronous.

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

Input Schema

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

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds real behavior beyond them: deletion is permanent, unshared variations go with it, externalId is released for reuse, and visitor-side propagation is asynchronous. The externalId-reuse note also explains the practical risk behind the non-idempotent hint, which the annotation alone cannot convey.

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?

Four short sentences, each adding a distinct fact: permanence and scope, id reuse, retry rule, async propagation. The most consequential information (permanence) is front-loaded with zero filler.

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

Completeness5/5

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

For a one-parameter destructive mutation with full annotation coverage and an output schema, the description covers everything an agent needs: irreversibility, cascade scope, id semantics, retry safety, and eventual consistency. Nothing material is left to inference.

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 100% for the single campaignId parameter, so the baseline would be 3. The description earns more by explaining that the id must be the immutable Grona id for retries and that externalId becomes reusable after deletion, which is behavioral meaning the schema does not carry.

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

Purpose5/5

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

States a specific verb and resource ('Permanently delete campaign') and adds the exact scope ('and unshared variations'), so an agent knows what is removed and what is not. No sibling in the catalog performs deletion, and the destructive framing clearly separates it from grona_set_campaign_status or grona_update_campaign.

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?

Gives concrete retry guidance ('Retry only by immutable Grona id'), which tells the agent how to safely re-attempt a failed call rather than reusing a freed externalId. It does not, however, state when to prefer this over a softer alternative such as pausing via grona_set_campaign_status, nor any preconditions like required permissions.

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