Skip to main content
Glama
tremendous-mcp

tremendous-mcp

by Bryan21B

Get campaign

get_campaign
Read-only

Retrieves a specific campaign, including its products and email settings, by campaign ID for review or configuration.

Instructions

Get one campaign with its products and email settings.

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": {
      "id": "<id>"
    },
    "name": "get_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.4/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 safety is covered. The description usefully adds that the response embeds related products and email settings, but stays silent on not-found behavior or whether related data is truncated.

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?

One sentence, zero waste, and the returned content is front-loaded. Nothing is padded, though there is also little structure to speak of.

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

Completeness3/5

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

For a read-only getter with one required id and no output schema, the description covers purpose and response shape adequately, but omits error/empty-result behavior and any indication of how embedded products and email settings are keyed.

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?

Schema description coverage is 0%, so the schema only says id is a string. The description's "one campaign" hints the id identifies a campaign, but it adds no format, source, or lookup detail beyond that inference. With a single obvious parameter the gap is small but real.

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?

"Get one campaign with its products and email settings" gives a specific verb (get), a precise scope (one), and discloses the payload contents (products, email settings). It is clearly distinct from list_campaigns, though it never names the alternative explicitly.

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 singular "one campaign" plus required id implies this is the single-record retrieval path and that list_campaigns is the browse path, but the description never states when to use this versus the list variant or what happens if the id is unknown.

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