ugc-brief-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| interpret_briefA | Paste a brand's UGC brief. Returns detected deliverables/specs/usage/disclosure, red flags (unlimited revisions, perpetual usage, spec work, raw-file grabs), and the exact questions to confirm in writing before agreeing. |
| get_brief_checklistA | The 10-point checklist every UGC brief must answer before you shoot: deliverables, usage, exclusivity, revisions, raw-vs-edited, specs, hooks, talking points, timeline, brand assets. |
| get_ugc_formatsA | The core UGC ad formats with structure and when to use each: testimonial, problem_solution, unboxing, demo_tutorial, get_ready_with_me, comparison, hook_test_pack. Omit format for all. |
| build_shot_listA | Given a UGC format, returns a beat-by-beat shot list template with coverage rules (shoot the hook 3 ways, get product close-up + in-use wide + reaction). Formats: testimonial, problem_solution, unboxing, demo_tutorial, get_ready_with_me, comparison, hook_test_pack. |
| scope_deliverablesA | Turn a vague ask into a defined deliverable list. Returns the exact fields to lock (count, format, length, aspect, revisions, raw-vs-edited, usage window) so nothing is left open to interpretation. |
| check_brief_red_flagsA | Scan a brief or message for production/scope red flags: unlimited revisions, perpetual usage, spec-first requests, raw-file grabs, vague deliverables, post-agreement scope creep. Returns flags + what to do. |
| get_full_packA | The complete UGC-brief library in one payload: formats, brief checklist, red flags. For full agent context. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Most tools have distinct purposes, but 'interpret_brief' and 'check_brief_red_flags' both deal with red flags, which could cause confusion. Descriptions help differentiate, with 'interpret_brief' being more comprehensive.
Naming follows a mostly consistent verb_noun pattern (e.g., get_ugc_formats, build_shot_list). Minor deviations like 'get_full_pack' (uses 'full' instead of a noun like 'library') are still clear.
Seven tools cover the UGC brief domain well without being excessive. Each tool has a clear role, from analyzing briefs to generating shot lists and scoping deliverables.
The tool set covers core UGC brief analysis and preparation tasks. Missing are tools for creating or editing briefs, but the given purpose (assisting with existing briefs) is well-served.