Skip to main content
Glama

UGC Agent

by app.ugcagent.mcp
OverviewDiscussionsAdmin

Create Lead Automation

create_lead_automation
Idempotent

Collect explicit values one missing field at a time in the returned order: criteria or Agent Preferences, lead_count, frequency, conditional weekday/day_of_month, exact daily_time, timezone, and an explicit recipient/account-email choice. Resolve 'local' or a city to a canonical IANA timezone before supplying timezone; never pass the literal 'local'. Once complete, creation writes immediately; the first run is scheduled for the returned next_run_at.

Input Schema

NameRequiredDescriptionDefault
uidNoOptional Firebase uid. Must match the URL uid unless local fallback is enabled.
weekdayNoISO weekday (1=Monday through 7=Sunday), required for weekly and biweekly.
criteriaNoCreator matching criteria, for example: Creators matching beauty skincare UGC in the UK.
timezoneNoCanonical IANA timezone for the schedule, resolved from the user's explicit answer; never the literal 'local'.
frequencyNoExplicit recurrence frequency; no default.
daily_timeNoRequested local delivery time in HH:mm, e.g. 09:30.
lead_countNoLeads per scheduled run, from 1 to 2,000.
bearer_tokenNoOptional Firebase ID token. Hosted clients normally authenticate with an API key in the Authorization header or ?uid= in the URL instead.
day_of_monthNoMonthly day, 1-28 or "last".
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.
recipient_emailNoExplicit delivery email.
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.
use_account_emailNoResolve the recipient from the authenticated Firebase profile email.
use_agent_preferencesNoUse the authenticated account's stored Agent Preferences as the criteria.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description provides essential behavioral context not found in the annotations or schema, specifically detailing the field collection order, the immediate write/scheduled run sequence, and the mandatory timezone canonicalization logic (never pass 'local').

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 dense but highly effective. Every sentence contributes critical operational instruction, including constraints on timezone handling and the execution timeline, demonstrating high informational efficiency.

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

Completeness5/5

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

The description is extremely complete regarding the implementation constraints. It handles the interaction pattern (multi-turn), system requirements (IANA conversion), and lifecycle of the object (immediate write/scheduled run) without needing to describe the output schema.

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?

Since schema description coverage is 100%, the baseline is high. The description adds value by dictating the conversational sequence of parameters (e.g., 'criteria or Agent Preferences' comes first, followed by 'lead_count'). It also adds the crucial constraint regarding timezone resolution.

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 tool clearly defines its function: creating a lead automation. Furthermore, the description goes beyond just the outcome by defining the *process* of data collection (collect explicit values one missing field at a time).

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

Usage Guidelines3/5

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

While it doesn't explicitly name sibling tools to contrast against, it provides detailed instructions on the mandatory multi-turn conversational flow required to use this tool. This conversational guidance helps the agent decide when this tool is necessary versus a simple configuration tool.

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