Skip to main content
Glama
Grona MCP

Grona MCP

by gbasilveira

Explain campaign

grona_campaign_overview
Read-onlyIdempotent

Reads a Grona campaign by ID and summarizes targeting, previews, variation health, and next steps. Use it to assess campaign status without creating editor links or assuming analytics data.

Instructions

Read campaign and summarize targeting, previews, variation health and next steps. Does not mint editor links or claim analytics exist.

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_campaign_overview"
  }
}

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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuine context by bounding expectations: no editor links are produced and analytics are not invented, which guards against hallucinated downstream assumptions. It says nothing about summarization depth, latency, or how 'next steps' are derived.

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?

Two compact sentences with the positive capability front-loaded and the exclusions following, no redundant restatement of the name. 'Next steps' is slightly hand-wavy, but nothing is padded or wasted.

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?

A read-only, single-parameter tool with an output schema and full annotation coverage needs little more than a clear statement of what the summary contains. The description supplies that plus scope exclusions; only the ambiguity of 'next steps' and the absence of any sibling routing keep it short of complete.

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?

There is a single required parameter with 100% schema description coverage, explicitly documented as an opaque campaign id or externalId. The description adds no syntax, format, or lookup semantics beyond that, so the schema carries the full burden and baseline 3 applies.

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 ('Read campaign and summarize') plus the exact facets returned: targeting, previews, variation health, next steps. This distinguishes it from a raw fetch like grona_get_campaign without naming it. However, it never explicitly contrasts itself with siblings such as grona_check_campaign_readiness, which sounds adjacent in intent.

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: reach for this when you want a consolidated read of a campaign rather than raw fields. The closing negatives ('Does not mint editor links or claim analytics exist') give a partial when-not boundary that implicitly routes toward editor-link and analytics tooling, but no alternative is named and no prerequisites are stated.

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