Skip to main content
Glama

Action campaign results

get_action_campaign_results
Read-only

Free, read-only. Every task's state (draft / available / held / in_review / done / closed), who holds it, clicks and sign-ups through its tracked link, and every proof (pending first) with its submission_id — show proofs to the user, then review_submissions. Also the cash pool and whether it is funded. Claims trickle in over days: check back later, don't poll.

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_id": "<campaign_id>"
    },
    "name": "get_action_campaign_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds substantive behavior beyond them: cost ('Free'), result ordering ('pending first'), the latency model ('claims trickle in over days'), and an explicit anti-pattern ('don't poll'). These are operational traits an agent cannot get from the structured fields and directly affect how it should call and re-call the tool.

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?

The most decision-relevant facts — free, read-only, what is returned, then review_submissions — are front-loaded, and nearly every clause carries information. It is a dense run-on paragraph rather than structured bullets, which slightly hurts scanability but not comprehension.

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?

With no output schema, the description must carry the entire return-value burden, and it does: it enumerates every returned field group, the state enum, proof ordering, and the cash pool. Combined with the freshness warning, an agent has everything needed to call this correctly and interpret the response.

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% and the single required campaign_id is undocumented in the schema, so the description would ideally clarify its format or source. The parameter is trivially inferable from the tool name and the campaign framing of the description, so this is a minor rather than serious gap — baseline 3.

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?

The description names the specific resource (action campaign results) and enumerates its contents: every task's state with the exact state vocabulary, who holds it, clicks and sign-ups via tracked link, every proof with submission_id, plus the cash pool and funding status. This is far more specific than the sibling names alone and lets an agent distinguish it from get_campaign_results or get_content_campaign_results.

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?

It gives a clear next-step routing rule — 'show proofs to the user, then review_submissions' — and a timing rule: 'Claims trickle in over days: check back later, don't poll.' What it lacks is an explicit statement of when to prefer this over the sibling results tools (get_campaign_results, get_content_campaign_results, get_campaign_activity), so the alternative selection is only partially covered.

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.