Skip to main content
Glama

One clipping campaign in detail

campaign_details
Read-onlyIdempotent

Everything known about one clipping campaign: rates per platform, cap, budget left and runway, approved clips, views, typical earnings per clip, and its brief. Pass the campaign id, slug or a heistclips/Content Rewards URL from rank_campaigns.

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": {
      "campaign": "<campaign>"
    },
    "name": "campaign_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignYesCampaign id, slug or URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered without the text. The description adds real value by enumerating what comes back (rates, cap, budget left, runway, earnings per clip), which matters because there is no output schema. It does not mention pagination, freshness, or behavior for unknown/nonexistent campaign ids.

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 the payload summary, then the calling instruction. No filler, no restated title, and the identifier requirement sits where the agent needs it.

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

Completeness5/5

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

For a single-parameter, read-only detail fetch with annotations covering safety, the description supplies the return contents that the absent output schema would otherwise carry, plus how to obtain the identifier. Nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 100% and the schema already says 'Campaign id, slug or URL', so the baseline is 3. The description earns an extra point by specifying the URL must be a heistclips/Content Rewards URL sourced from rank_campaigns, which constrains acceptable input beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb-plus-resource: retrieves everything about ONE campaign, and enumerates the exact payload (rates per platform, cap, budget left, runway, approved clips, views, typical earnings, brief). The phrase 'one clipping campaign' clearly separates it from the sibling rank_campaigns, which is the list/ranking view.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Pass the campaign id, slug or a heistclips/Content Rewards URL from rank_campaigns' establishes the workflow context and the source of the identifier, so an agent knows this is the detail step after ranking. It stops short of stating exclusions or when-not-to-use, so it is clear context rather than a full when/when-not rule set.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.