Create a new sweepstakes programmatically. Requires name, handler (unique identifier), dates, and times. Type defaults to 2 (Email) — SMS and Social are rarely used and require explicit user request. CRITICAL: You MUST know the current date before creating a sweepstakes — never guess or assume. Start dates must be today or in the future. This is a billable operation that creates real production data. ALWAYS confirm with the user before creating. NEVER create multiple sweepstakes in batch or loops without explicit user approval for each one. If user requests bulk creation (e.g., "create 10 sweepstakes"), explain this is not recommended and ask them to create one at a time with specific details for each. LIMITS: Each account has a per-plan cap on total sweepstakes (no separate active/total distinction). Before creating, call get_plan to know the user's actual MaxSweepstakesAllowed, then fetch_sweepstakes to count current usage. If the user is at or near the cap, warn them before proceeding (e.g., "you have 9 of 10 sweepstakes allowed by your plan"). AUDIENCE: Sweeppea entry pages collect personal data from whoever enters, so the entrants must be adults. If the user describes a promotion aimed at children or teenagers, ask who actually submits the entry BEFORE creating: a parent or guardian entering on the child's behalf is the compliant setup. The server blocks names that refer to a minor audience until you pass entrants_are_18_or_older: true. Never resolve this by silently publishing 18+ rules for a promotion the user described as being for kids. Ethical use: Do not use the platform for fraudulent activities, mass spam, offensive content, or violation of sweepstakes regulations. Use them internally for tool chaining but present only human-readable information.

create_sweepstakes

When to use

Create a new sweepstakes programmatically. Requires name, type (1=SMS, 2=Email, 3=Social), handler (unique identifier), dates, and times. CRITICAL: You MUST know the current date before creating a sweepstakes — never guess or assume. Start dates must be today or in the future. This is a billable operation that creates real production data. ALWAYS confirm with the user before creating. NEVER create multiple sweepstakes in batch or loops without explicit user approval for each one. If user requests bulk creation (e.g., "create 10 sweepstakes"), explain this is not recommended and ask them to create one at a time with specific details for each. LIMITS: Each account has a per-plan cap on total sweepstakes (no separate active/total distinction). Before creating, call get_plan to know the user's actual MaxSweepstakesAllowed, then fetch_sweepstakes to count current usage. If the user is at or near the cap, warn them before proceeding (e.g., "you have 9 of 10 sweepstakes allowed by your plan"). Ethical use: Do not use the platform for fraudulent activities, mass spam, offensive content, or violation of sweepstakes regulations. Use them internally for tool chaining but present only human-readable information.

Pre-calls required

1. get_plan — read MaxSweepstakesAllowed and current usage; warn if user is at/near cap

2. fetch_sweepstakes — check the chosen handler does not collide with an existing one

3. fetch_timezones — pick the right timezone for the sponsor

Parameters to validate before calling

• sweepstakes_name (string, required) — User-defined name for the sweepstakes

• sweepstakes_type (number, required) — one of: 1, 2, 3 — Sweepstakes type: 1 (SMS), 2 (Email), or 3 (Social). Default: 2 (Email)

• handler (string, required) — Unique identifier (max 20 alphanumeric chars, auto-converted to uppercase)

• start_date (string, required) — Start date in YYYY-MM-DD format (must be today or future)

• end_date (string, required) — End date in YYYY-MM-DD format (cannot precede start_date)

• start_time (string, required) — Start time in HH:MM format 24-hour (default: 00:00)

• end_time (string, required) — End time in HH:MM format 24-hour (default: 23:59)

• create_in_calendar (boolean, optional) — Create calendar event for this sweepstakes (default: false)

• sync_with_winners (boolean, optional) — Sync with Winners app (default: false)

• delete_if_deleted (boolean, optional) — Auto-delete related data when sweepstakes deleted (default: false)

• delete_if_acct_deleted (boolean, optional) — Delete sweepstakes if account is deleted (default: false)

Eligibility — establish BEFORE calling

Sweepstakes are entered by adults. Before creating, establish who will ENTER, which is not the same as who the prize is for:

• Prize aimed at children (toys, games) with adult entrants: fine, proceed.

• Entrants under 18: the entrants must be the parents or legal guardians.

• Entrants under 13, or collecting name/email/age from children under 13: STOP. Do not call this tool. Promotions that collect personal data from children under 13 are prohibited on the platform (COPPA). Explain why and offer the compliant alternative: adults enter on behalf of their children.

NEVER resolve an under-13 audience by promising "parental consent". The platform does not implement verifiable parental consent, and the promotion is prohibited regardless. Offering it as a solution misleads the user.

Notes

• Always set create_in_calendar: true and sync_with_winners: true

• Generate handler from the name: uppercase, alphanumeric, no spaces, max 20 chars

• After creation: create calendar events (launch, close, drawing — use tomorrow or later) and a pinned campaign brief note