Skip to main content
Glama

Read a UGC campaign

autoshort_ugc_get_campaign
Read-onlyIdempotent

Retrieve a Silent UGC campaign's character, recording, suggested hooks, and every variant with status, preview, and finished video download URL.

Instructions

Read a Silent UGC campaign: character, recording, suggested hooks, and every variant with its status, preview and finished videoUrl (download). Free.

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": {
      "campaignId": "<campaignId>"
    },
    "name": "autoshort_ugc_get_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: the exact contents of the response (including per-variant status and a downloadable finished videoUrl) and the cost signal 'Free,' which matters in a product that otherwise charges credits. It stops short of saying how an in-progress campaign is represented or what happens with an unknown campaignId.

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?

One sentence with a colon-delimited payload list, front-loaded with the verb and resource. Every element earns its place, and the trailing 'Free.' is a compact, high-value cost signal rather than padding.

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 one-parameter read tool with no output schema, the description usefully compensates by describing the returned fields and noting it is free, and annotations cover safety. What remains missing is the meaning and provenance of campaignId and any hint about the state machine (e.g. variants pending vs. finished), which matters for a tool whose output includes statuses and a not-yet-populated videoUrl.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter campaignId has 0% schema description coverage, so the description carries the full burden and fails to meet it — campaignId is never mentioned, nor where to obtain it (presumably from autoshort_ugc_create_campaign). An agent must guess the id format and source. This is the definition's largest gap.

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 leads with a specific verb and resource ('Read a Silent UGC campaign') and then enumerates the payload: character, recording, suggested hooks, and variants with status, preview and finished videoUrl. That is far more concrete than the title alone. It does not explicitly contrast itself with siblings such as autoshort_ugc_create_campaign, though the read/create split is largely self-evident from the verb.

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?

Usage is only implied: an agent can infer this is the call to inspect a campaign after creating or rendering it, especially since the description reveals the finished videoUrl for download. There is no explicit when-to-use, no guidance on polling until variants finish, and no named alternative for listing or previewing campaigns.

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