Skip to main content
Glama
Grona MCP

Grona MCP

by gbasilveira

List campaigns

grona_list_campaigns
Read-onlyIdempotent

Lists every campaign in the workspace with its variations and previews; results are unpaginated and editor links are omitted.

Instructions

Return every workspace campaign with variations and previews. No upstream pagination or specified order; editor links are omitted.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "grona_list_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description still adds real value by disclosing that there is no upstream pagination, that result order is unspecified, and that editor links are deliberately omitted — three traits an agent cannot get from the structured fields.

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?

Two sentences, front-loaded with what is returned and followed by the operational caveats. No repetition of the title and no filler.

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?

An output schema exists, so return-value shape need not be described, and the description still covers scope, ordering and omissions. The only untested area is payload volume on large workspaces, which the no-pagination note hints at but does not quantify.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to compensate for. The schema's empty properties object is fully consistent with a no-argument enumeration call.

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?

"Return every workspace campaign with variations and previews" gives a specific verb plus resource and states the payload contents, which implicitly separates it from a filtered search tool. It stops short of naming grona_search_campaigns, so the differentiation must be inferred from the word "every".

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 only implied: the agent can infer this is the full-enumeration tool and that filtered lookups belong elsewhere, but no alternative is named and no when-not-to-use condition is stated. It is adequate rather than instructive.

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