Skip to main content
Glama

UGC Agent

by app.ugcagent.mcp
OverviewDiscussionsAdmin

Draft Creator Outreach

draft_creator_outreach
Read-onlyIdempotent

Draft short, direct outbound copy (DM and/or email) for contacting a creator. Keeps it concise and never invents pay, proof, clients, or results. Use it after keeping leads to write personalized outreach.

Input Schema

NameRequiredDescriptionDefault
ctaNoOne next step, e.g. 'Open to seeing the brief and rates?'
uidNoOptional Firebase uid. Must match the URL uid unless local fallback is enabled.
channelNoWhich format to draft. Use 'both' when the user asks for DMs and emails.
brand_nameNoBrand, product, agency, or program name.
proof_pointNoOne credible proof point supplied by the user. Omit vague or unverified claims.
sender_nameNoSender's first name or full name, if known.
sender_roleNoSender role/title, e.g. Head of Creators or Growth Lead.
bearer_tokenNoOptional Firebase ID token. Hosted clients normally authenticate with an API key in the Authorization header or ?uid= in the URL instead.
compensationNoPay/bonus details the user provided. Omit if unknown; never invent rates.
collaborationNoThe concrete creator work, e.g. '10-20 short TikTok videos per week' or 'short UGC product demos'.
recipient_nameNoCreator first name, or omit to use a {First Name} placeholder.
company_contextNoOne short factual sentence about what the brand/product/program does.
conversation_idNoCreator-list key for durable state. Reuse a returned list_id for follow-ups; when omitted, MCP uses the active generated list for this tool chain.
personalizationNoOne specific reason this creator is a fit. Keep it short.
preferences_modeNoHow to apply preferences for this call: 'stored' uses users/{uid}.agentPreferences, 'override' uses agent_preferences only, and 'none' disables stored filtering for this run.
agent_preferencesNoOptional per-call filtering preferences. Use with preferences_mode='override'. For backwards compatibility, passing this without preferences_mode implies override.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description provides a vital behavioral guardrail that annotations cannot cover: the prohibition against fabricating information ('never invents pay, proof, clients, or results'). This ensures the AI uses the tool responsibly and maintains data integrity.

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?

The description is highly efficient, using only two sentences. It front-loads the primary function and then uses the second sentence to establish necessary context and strict limitations.

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 text generation tool, the input structure is highly complete. The description successfully sets the scope and limitations of the draft. A score of 4 is given only because it lacks an explicit output schema, which would be helpful for confirming the format of the generated copy.

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?

Since the input schema has 100% coverage, the description does not need to define parameters beyond their existing documentation. It only adds semantic value by implying the overall output style must be 'short' and 'direct'.

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?

The purpose is extremely clear: to draft short, direct outbound copy specifically for creators. It distinguishes itself from other tools by focusing on drafting/copy generation, rather than sending or analyzing.

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?

It provides clear sequential instructions: 'Use it after keeping leads to write personalized outreach.' Furthermore, the critical constraint, 'never invents pay, proof, clients, or results,' defines a strict behavioral boundary for when the tool is appropriate to use.

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

All UGC Agent 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