Skip to main content
Glama

UGC in-action pipeline

adgpt_in_action

Talking-head / UGC-in-action wizard for a SAC campaign: generate scripts, strategies, and per-character plans; preview voices; tag scripts; persist wizard state. Read adgpt://pipeline/characters and adgpt://pipeline/voices first. In-action and commercial videos need a Pro plan or higher. Actions: generatePipelineScripts, generateStrategies, generatePlan, plans, getWizardState, saveWizardState, tagScript, voicePreview, voicePreviewStatus. Call adgpt_capabilities with the operationId to see an action's parameters.

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": {
      "action": "<action>"
    },
    "name": "adgpt_in_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoParameters for the action (see adgpt_capabilities).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is covered; the description adds value beyond that by disclosing the required resource reads and the Pro-plan entitlement gate. It does not clarify which of the nine actions are mutating (saveWizardState, tagScript) versus read-only, nor whether voicePreview is asynchronous beyond the presence of a status action.

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 description is front-loaded with the wizard's purpose, then prerequisites, gating, and the action surface, with no filler sentences. The inline enumeration of all nine actions duplicates the schema enum and consumes space that could have gone to per-action intent, but it remains scannable.

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 router-style tool with nine actions, a nested untyped params object, and no output schema, the description covers prerequisites and plan gating but leaves the semantics of individual actions (what 'plans' returns, what 'generatePlan' produces) to the adgpt_capabilities lookup. That delegation is reasonable but means the definition alone is not sufficient to invoke a specific action confidently.

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?

With only two parameters and 50% schema coverage, the description's main contribution is listing the nine action names and directing the agent to call adgpt_capabilities with the operationId for per-action parameters. That delegation is useful, but the action list merely echoes the schema enum, and the free-form 'params' object remains entirely opaque without a follow-up call.

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 gives a specific verb+resource framing — a 'talking-head / UGC-in-action wizard for a SAC campaign' that generates scripts, strategies, plans, previews voices, tags scripts, and persists state — so an agent knows exactly what domain this tool covers. It differentiates itself by the 'wizard/pipeline' framing rather than by naming the closest sibling (adgpt_ugc), 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 Guidelines4/5

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

It provides concrete pre-call context: read adgpt://pipeline/characters and adgpt://pipeline/voices first, and in-action/commercial videos require a Pro plan or higher. What is missing is any explicit routing advice versus the sibling tools (adgpt_ugc, adgpt_recreation, adgpt_job) or a statement of when not to use this wizard.

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.

Resources