Skip to main content
Glama
Grona MCP

Grona MCP

by gbasilveira

Search campaigns

grona_search_campaigns
Read-onlyIdempotent

Search and filter campaigns by text, status, type, domain, script state, or external ID, then sort results deterministically with local offset/limit controls for navigation.

Instructions

Fetch full list once; filter locally by text/status/type/domain/script state/externalId and sort deterministically. offset/limit are local presentation controls.

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

Input Schema

NameRequiredDescriptionDefault
typeNo
limitNo
orderNoasc
queryNoCase-insensitive substring of name, id, externalId or domain.
domainNo
offsetNo
sortByNoname
statusNo
externalIdNo
scriptStatusNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description's genuinely useful addition is that filtering and sorting happen client-side and that offset/limit are presentation-only, which is non-obvious. It does not clarify whether the default limit of 100 truncates the fetched set, which is a behavioral gap for an agent expecting a full list.

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 compact sentences with the core fetch-once/filter-locally model front-loaded and the pagination caveat second. Every clause carries information and there is 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 values need not be explained, and the description covers the essential execution model for a 10-parameter tool. The remaining gap is whether limit caps the returned rows and how that interacts with 'full list', which an agent would need to know.

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?

With only 10% schema description coverage, the description has to carry the load, and it does add real meaning: it enumerates the filterable facets (text/status/type/domain/script state/externalId) and reframes offset/limit as local presentation controls rather than server-side paging. It still leaves the limit maximum of 1000 and the asc/desc order parameter unaddressed.

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?

The description states a specific behavior: fetch the full campaign list once, then filter locally by several named facets and sort deterministically. It is clear what the tool does, but it never names the sibling list tool it supersedes, so differentiation from grona_list_campaigns relies on the name alone.

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?

The instruction 'Fetch full list once; filter locally' implies a usage pattern (prefer one fetch with client-side filtering over repeated paginated queries), but there is no explicit when-to-use/when-not guidance and no named alternative such as grona_list_campaigns or grona_get_campaign.

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