Skip to main content
Glama

UGC presenter catalogs

adgpt_ugc
Read-only

Browse the UGC presenter avatar and voice catalogs. (UGC videos themselves are generated through adgpt_campaigns, adgpt_single_asset and adgpt_in_action.) Actions: avatarsPaginated, voices. 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_ugc"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoParameters for the action (see adgpt_capabilities).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description carries a lower bar; it correctly characterizes the tool as browsing catalogs. However, the action name avatarsPaginated implies paging semantics that are never described (page size, cursors, total counts), and there is no output schema to fill that gap.

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?

Three short sentences, front-loaded with the purpose, then the scope exclusion, then the parameter-discovery hint. The 'Actions: avatarsPaginated, voices.' clause duplicates the enum already visible in the schema and could be dropped without loss.

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 two-parameter read tool this covers the essentials and correctly hands parameter detail off to adgpt_capabilities. With no output schema, though, an agent still cannot anticipate the shape of paginated avatar/voice results or how pagination is expressed, which is a real gap for an operation literally named 'Paginated'.

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 coverage is 50%: the action enum is already documented in the schema, so restating 'avatarsPaginated, voices' adds little. The nested params object is opaque and the description defers entirely to adgpt_capabilities, which is useful routing but does not supply any parameter meaning itself.

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?

States a concrete verb and resource — browsing the UGC presenter avatar and voice catalogs — and explicitly separates that concern from video generation, which is done via named sibling tools. The title and first sentence are near-duplicates, so the win comes from the sibling disambiguation rather than the headline itself.

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?

Gives an explicit when-not-to-use path by naming adgpt_campaigns, adgpt_single_asset and adgpt_in_action for actual generation, plus a second pointer to adgpt_capabilities for action parameters. What is missing is guidance on choosing between the two actions (avatarsPaginated vs voices) or when to pick this over adgpt_catalog.

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