Skip to main content
Glama

UGC Fans

by fans.ugc
OverviewDiscussionsAdmin

Write a script, hooks or a translation

ugcfans_write_script

Writes an ad script from a product or a web page, or, given a saved script, writes alternative opening hooks for it or translates it, and returns a job whose result holds the script. Spends a few of the account's credits only with a held quote. Without one, returns the cost and makes nothing. Give product or page_url to write a new script; give script with hooks (how many) or with translate_to (a language) to work on one.

Input Schema

NameRequiredDescriptionDefault
angleNoThe angle or hook to take.
brandNoThe id of a saved brand whose voice to follow.
hooksNoWith script: how many alternative openings to write.
offerNoThe offer or call to action.
quoteNoThe held quote for this exact request, after the person confirms its cost.
pointsNoPoints the script should make.
scriptNoThe id of a saved script to work on, from an earlier ugcfans_write_script.
productNoWhat is being sold, in a sentence or two.
secondsNoHow long the ad runs, 5 to 120 (default 30).
audienceNoWho the ad is for.
languageNoThe language to write in (default English).
page_urlNoA web page to read the product from, instead of product.
translate_toNoWith script: the language to translate it into.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / quote
      Added value: +{
+  "description": "The held quote for this exact request, after the person confirms its cost.",
+  "maxLength": 4096,
+  "type": "string"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnly=false/destructive=false/idempotent=false, but the description goes well beyond them: it discloses credit consumption, the quote-hold confirmation flow ('without one, returns the cost and makes nothing'), and that the call is asynchronous, returning a job whose result holds the script. This is exactly the billing and async behavior an agent needs before invoking.

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?

Four sentences, front-loaded with the core action and mode enumeration, then billing behavior, then parameter routing. Dense but every sentence earns its place; no filler or restatement of the title.

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

Completeness4/5

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

For a 13-parameter, zero-required, no-output-schema tool, the description covers the modes, the credit/quote gate, and the job-return shape. It omits guidance on polling the returned job (ugcfans_get_job/ugcfans_wait_job) and on which parameter combinations are invalid, but nothing essential to invoking 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%, so the baseline is 3, but the description adds genuine cross-parameter semantics the schema cannot express — that product/page_url select the 'new script' mode while script+hooks or script+translate_to select the 'work on existing script' mode. It does not cover defaults for seconds/language beyond what the schema states.

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?

States a specific verb+resource ('Writes an ad script') and enumerates all three operating modes (new script from product/page_url, alternative hooks from a saved script, translation). An agent can distinguish this from siblings like ugcfans_make_ad or ugcfans_estimate without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit routing rules: 'Give product or page_url to write a new script; give script with hooks (how many) or with translate_to (a language) to work on one.' It also states the when-not condition for the quote parameter — without a held quote nothing is made and only a cost is returned.

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

All UGC Fans toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources