Skip to main content
Glama
tremendous-mcp

tremendous-mcp

by Bryan21B

List campaigns

list_campaigns
Read-only

Lists Tremendous campaigns so you can find a campaign_id to use when sending rewards; each campaign defines products, message, and branding.

Instructions

List Tremendous campaigns (reward templates with products, message and branding). Use a campaign_id in send_rewards.

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": "list_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context that campaigns are reward templates carrying products, message and branding, plus the link to send_rewards. It does not mention pagination, result size, or whether all campaigns are returned at once, which is the main remaining behavioral gap.

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 short sentences with no filler: the resource and its definition come first, followed by the actionable consumption hint. Every clause earns its place.

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?

For a zero-parameter read-only list with no output schema, the description covers what the resource is and how its IDs are used elsewhere. The only missing piece an agent might want is return cardinality or pagination behavior, which is minor at this complexity.

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 of 4 applies; there is nothing for the description to disambiguate. The mention of campaign_id clarifies that the IDs returned by this tool are the ones consumed by send_rewards, which is meaningful downstream semantics.

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 and resource ('List Tremendous campaigns') and goes further by defining what a campaign is (reward templates with products, message and branding). That parenthetical makes the resource concrete. It separates it from non-list siblings like get_campaign only implicitly via 'List', so it stops short of a 5.

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 second sentence is a downstream-consumption hint ('Use a campaign_id in send_rewards'), which tells the agent where campaign IDs go rather than when to call this tool. There is no explicit guidance on when to use this versus get_campaign or the other list_* tools. Usage is implied by the name and resource, not spelled out.

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