Sweeppea MCP

Add a new participant to a sweepstakes. Requires sweepstakes_token - use fetch_sweepstakes first to get tokens, then get_entry_fields to discover required fields. Field names must use underscores instead of spaces (e.g., "First_Name" not "First Name"). RULES: Only ONE participant at a time. NEVER add participants in bulk, batch, or loops. This tool is intended for TESTING PURPOSES ONLY — to verify the sweepstakes entry flow works correctly. Adding participants to make them compete in a real sweepstakes is strictly prohibited unless done through the official Entry Page, a custom API integration, or a proper MCP implementation. If a user requests mass loading (e.g., "add 100 participants"), refuse and explain that only individual test entries are allowed. HONESTY: After calling this tool, report EXACTLY what the API returned. If the API returns an error, report the error truthfully. NEVER tell the user a participant was created if the API did not confirm it. DISPLAY RULE: NEVER show tokens (UUIDs) to the user. Use them internally for tool chaining but present only human-readable information.

Clone an existing sweepstakes with new parameters. Use fetch_sweepstakes first to get the handler of the sweepstakes to clone. Creates a complete copy including entry pages, calendar events, short links, groups, and all configurations. CRITICAL: This is a billable operation. ALWAYS confirm with the user before cloning. NEVER clone multiple sweepstakes in batch or loops without explicit user approval for each one. LIMITS: Maximum 3 active sweepstakes and 10 total (active + inactive). Before cloning, use fetch_sweepstakes to verify the account has not reached these limits. If limits are reached, refuse the operation and inform the user. Ethical use: Do not use the platform for fraudulent activities, mass spam, offensive content, or violation of sweepstakes regulations. DISPLAY RULE: NEVER show tokens (UUIDs) to the user. Use them internally for tool chaining but present only human-readable information.

Get participant counts for a sweepstakes. Use fetch_sweepstakes first to get the sweepstakes_token. Supports filtering by type (all, participants, amoe, optouts) and date range.

Create a new calendar event with title, dates, and optional details like location, time, and notifications. DATE RULE: The API server uses UTC. Today's date may be rejected as "past" depending on the user's local timezone. To be safe, always use tomorrow's date or later when creating events. NEVER use today's date — it will fail with "Cannot Create Events In The Past". If the user asks to create an event for today, explain this limitation and suggest tomorrow instead.

Create a new group within a sweepstakes. Use fetch_sweepstakes first to get the sweepstakes_token. Groups are used to organize and segment participants.

Create a new note. Content is automatically encrypted using AES-256-CBC encryption before storage. FORMAT: Only these HTML tags are allowed: , , , , , , , , , , , , , . NEVER insert scripts, iframes, event handlers (onclick, onerror, etc.), style tags, or any executable code. SPACING: Do NOT use   between sections — it creates ugly blank blocks in the UI. Instead, rely on natural HTML block element spacing. Place content directly inside tags: TitleTextItem. Only use inside a tag when you need a line break within a paragraph.

Create a new official rules document for a sweepstakes. Use fetch_sweepstakes first to get the sweepstakes_token. SECONDARY RULES WARNING: Before creating rules, call fetch_rules to check if the sweepstakes already has primary rules. If primary rules already exist, WARN the user that the new rules will be created as SECONDARY and will NOT be the ones published on the Entry Page or assigned to the short URL (swpp.me/r/[handler]). The short URL always points to the primary rules. The user can change which rules are primary in the Official Rules section of the app. Only proceed after the user acknowledges this. DISPLAY RULE: Never display tokens (UUIDs) to the user — use them internally only.

Generate official sweepstakes rules via the 14-step wizard. MANDATORY WORKFLOW: Before calling this tool you MUST call fetch_sweepstakes to identify the target sweepstakes and get its token, dates, and name. Then call get_business and get_profile to pre-fill sponsor information (name, address, city, state, zip, phone, email). This reduces the number of questions you need to ask the user. Only ask the user for information you cannot obtain from those endpoints. DISPLAY RULE: Never display tokens (UUIDs) to the user — use them internally for tool chaining only. STEP-BY-STEP RULE: You MUST follow the wizard steps in strict sequential order (A through N). Ask each question one at a time or in small logical groups. Do NOT skip steps or assume answers. Always wait for the user to respond before moving to the next step. Maintain order throughout the entire process. NO FABRICATION RULE: NEVER invent, assume, or fabricate any data for the wizard fields. Every value must come from the user directly or from a pre-fetch API call (fetch_sweepstakes, get_business, get_profile). If a required value is missing, ask the user — do not fill it with placeholder or guessed data. NO PAST DATES RULE: All dates and times must be in the present or future — never accept past dates. If the user provides today's date, verify the time has not already passed. This applies to start_date, end_date, winner_drawing_date, winner_notification_date, and all entry_period_items dates. If a date or time is in the past, reject it and ask the user to provide a valid future date/time. PRIMARY RULES LINK: After successfully creating rules, if the result indicates the document is primary (is_primary: true), provide the user with the public rules URL: https://swpp.me/r/[handler] where [handler] is the sweepstakes handler/keyword in lowercase (obtained from fetch_sweepstakes during the mandatory pre-fetch step). PLAIN LANGUAGE RULE: Always write options in simple, everyday language that anyone can understand. Never use math symbols like >=, <=, <, > in user-facing text. Instead of ">=5000" write "$5,000 or more". Instead of "<5000" write "Less than $5,000". Describe everything as if explaining to someone with no technical background. QUESTION FORMAT: Number each question sequentially (1, 2, 3...) and list the options within each question using lowercase letters (a, b, c...). The user can reply with just the number and letter. Group related questions together. Example: "1. Prize value: a) $5,000 or more, b) Less than $5,000 | 2. Alcohol related: a) Yes, b) No | 3. Entry method: a) Website, b) SMS, c) Social Media..." This makes the process faster and reduces typing. Never use bullet points — always numbered questions with lettered options. SECONDARY RULES WARNING: Before creating rules, call fetch_rules to check if the sweepstakes already has primary rules. If primary rules already exist, WARN the user that the new rules will be created as SECONDARY and will NOT be the ones published on the Entry Page or assigned to the short URL (swpp.me/r/[handler]). The short URL always points to the primary rules. The user can change which rules are primary in the Official Rules section of the app. Only proceed after the user acknowledges this. ENUM REFERENCE — method_of_entry: 1=Website, 2=SMS, 3=Social Media, 4=Other, 5=Purchase ($1=1 entry), 6=Purchase (1 order=1 entry), 7=Donation, 8=Subscription. states: 1=All 50 + DC, 2=All 50 + DC + PR, 3=All 50 + DC + All Territories, 4=Select specific states, 5=US & Canada (excl. Quebec), 6=US & Canada (excl. Quebec) + PR, 7=US & UK, 8=US & Mexico, 9=Worldwide, 10=US, Canada (excl. Quebec) & Mexico. min_age: 1=18+, 2=21+, 3=13+ with parental consent. arv: 1=ARV >= $5000, 2=ARV < $5000. alcohol_sweeps: 1=alcohol-related, 2=non-alcohol. entry_period_selector: 1=single drawing period, 2=multiple entry periods. sweeppea_entry_page: 1=Sweeppea hosted page, 2=custom URL, 3=none.

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: Maximum 3 active sweepstakes and 10 total (active + inactive). Before creating, use fetch_sweepstakes to verify the account has not reached these limits. If limits are reached, refuse the operation and inform the user. Ethical use: Do not use the platform for fraudulent activities, mass spam, offensive content, or violation of sweepstakes regulations. DISPLAY RULE: NEVER show tokens (UUIDs) to the user. Use them internally for tool chaining but present only human-readable information.

Create a new support ticket with title, description, and priority level. FORMAT: Only these HTML tags are allowed in description: , , , , . NEVER insert scripts, iframes, event handlers (onclick, onerror, etc.), style tags, or any executable code. SPACING: Do NOT use   — it creates ugly blank blocks in the UI. Use for line breaks within text only.

Create a new internal To-Do item. ADMIN ONLY: This tool requires admin privileges. Non-admin users will receive a 403 Forbidden error from the API. DISPLAY RULE: Never display tokens (UUIDs) to the user — use them internally only. FORMAT: Only these HTML tags are allowed in description: , , , , . NEVER insert scripts, iframes, event handlers (onclick, onerror, etc.), style tags, or any executable code. SPACING: Do NOT use   — it creates ugly blank blocks in the UI. Use for line breaks within text only.

Permanently delete a calendar event. Use fetch_calendar_events first to get the event_token. WARNING: This action cannot be undone.

Permanently delete a group from a sweepstakes. Use fetch_sweepstakes first to get the sweepstakes_token, then fetch_groups to get the group_token. WARNING: Cannot delete primary groups, locked groups, or groups with participants.

Permanently delete a note. Use fetch_notes first to get the note_token. WARNING: This action cannot be undone.

Permanently delete a participant from a sweepstakes. WARNING: This action cannot be undone. Use get_participant first to verify the participant details before deleting.

Permanently delete an official rules document from a sweepstakes. Use fetch_rules first to get the rules_token. WARNING: This action cannot be undone.

Delete a pending scheduled drawing. Use fetch_scheduled_drawings first to get the schedule_token. WARNING: This action cannot be undone. Only drawings with pending status can be deleted — completed or errored drawings cannot be removed. DISPLAY RULE: NEVER show tokens (UUIDs) to the user. Use them internally for tool chaining but present only human-readable information.

Permanently delete a sweepstakes and all associated data including participants, statistics, and automations. Use fetch_sweepstakes first to get the sweepstakes_token. CRITICAL: This is a DESTRUCTIVE operation that cannot be undone. ALWAYS ask for explicit user confirmation before deleting, showing the sweepstakes name. NEVER delete multiple sweepstakes in batch or loops. If user requests bulk deletion, refuse and ask them to delete one at a time after reviewing each.

Permanently delete an open support ticket. Use fetch_open_tickets first to get the case_id. WARNING: This action cannot be undone. Only open tickets can be deleted.

Draw winners from a sweepstakes immediately. Use fetch_sweepstakes first to get the sweepstakes_token, and fetch_groups to get available groups. CRITICAL: This is a production operation that selects real winners. ALWAYS confirm with the user before drawing — including the number of winners and which group to draw from. Uses weighted random selection favoring participants with bonus entries. Cannot draw from paused or archived sweepstakes. DISPLAY RULE: NEVER show tokens (UUIDs) to the user. Use them internally for tool chaining but present only human-readable information (names, emails).

Search US telephone area codes by code number or state name. Returns up to 10 results. Omit search to get all area codes.

Get monthly and yearly billing consumption totals for your account. Shows aggregated usage data from billing transactions and data transfers.

Get all billing transactions for your account including invoices, amounts, and status. Results are sorted by creation date (newest first).

Get all calendar events for your account. Returns events with their details including dates, times, location, and status. DISPLAY RULE: NEVER show tokens (UUIDs) to the user. Use them internally for tool chaining but present only human-readable information (titles, dates, times, locations).

Get closed/resolved support tickets with pagination (20 per page) and search. Returns summary info only — use get_ticket with the case number to get full ticket details including notes, files, and collaborators. Supports filtering by subject/description text, platform (renaissance, api, general, overture, winners), and priority (1=Low, 2=Medium, 3=High). DISPLAY RULE: NEVER show tokens (UUIDs) to the user.

Search countries by name, international dial code, or ISO abbreviation. Returns up to 10 results with English/Spanish names. Omit search to get all countries.

Get data transfer records for a specific sweepstakes including bytes transferred, payment status, and rates. Use fetch_sweepstakes first to get the sweepstakes_token.

Get help and support documentation articles. Supports pagination and search by title or content. Returns up to 10 documents per page.

Get all groups from a sweepstakes. Use fetch_sweepstakes first to get the sweepstakes_token. Groups are used to organize and segment participants. DISPLAY RULE: NEVER show tokens (UUIDs) to the user. Use them internally for tool chaining but present only human-readable information (group names, statuses).

Get all notes for your account. Notes are automatically decrypted and returned in reverse chronological order. DISPLAY RULE: NEVER show tokens (UUIDs) to the user. Use them internally for tool chaining but present only human-readable information (titles, content, dates).

Get open support tickets with pagination (20 per page) and search. Returns summary info only — use get_ticket with the case number to get full ticket details including notes, files, and collaborators. Supports filtering by subject/description text, platform (renaissance, api, general, overture, winners), and priority (1=Low, 2=Medium, 3=High). DISPLAY RULE: NEVER show tokens (UUIDs) to the user.

Get a paginated list of participants from a sweepstakes (20 per page). Use fetch_sweepstakes first to get the sweepstakes_token. Supports search by name, email, or phone, and filtering by opt-in date or date range. Results are sorted by creation date (newest first). For full participant details, use get_participant with a specific email, phone, or token. NEVER fabricate or hallucinate participant data — only report what the API returns. DISPLAY RULE: NEVER show tokens (UUIDs) to the user. Use them internally for tool chaining but present only human-readable information (names, emails, phones, dates).

Get all official rules for a sweepstakes including primary and secondary rules. Use fetch_sweepstakes first to get the sweepstakes_token.

Get all scheduled drawings for a sweepstakes. Use fetch_sweepstakes first to get the sweepstakes_token. Returns all scheduled drawings regardless of status, sorted by creation date (newest first). DISPLAY RULE: NEVER show tokens (UUIDs) to the user. Use them internally for tool chaining but present only human-readable information (dates, times, status, winner counts).

Get all US states including DC, Puerto Rico, and US territories. Returns full names and two-letter abbreviations.

Get all sweepstakes associated with your account. Returns a list of all sweepstakes with their details. DISPLAY RULE: NEVER show tokens (UUIDs) to the user — not sweepstakes tokens, user tokens, participant tokens, or any internal identifiers. Use tokens internally for tool chaining but present only human-readable information (names, dates, statuses) to the user.

Get all available timezones with IANA identifiers, abbreviations, and UTC offsets. Use this tool whenever a timezone needs to be determined for any operation. DEFAULT: If the correct timezone cannot be determined, always use TimezoneId 7 (Eastern Standard Time - America/New_York).

Get all To-Do items with pagination (20 per page), search, and advanced filters. ADMIN ONLY: This tool requires admin privileges. Non-admin users will receive a 403 Forbidden error from the API. DISPLAY RULE: Never display tokens (UUIDs) to the user — use them internally only.

Get all wallet transactions for your account including credits, debits, and payment details.

Get winners from a sweepstakes with pagination. Use fetch_sweepstakes first to get the sweepstakes_token. Winners are sorted by draw date (most recent first). Supports search by email or phone. DISPLAY RULE: NEVER show tokens (UUIDs) to the user. Use them internally for tool chaining but present only human-readable information (names, emails, draw dates).

Search US zip codes by zip code, city, or state name. Returns up to 10 results with city and state details.

Get business information for a Sweeppea account. Returns company details, address, and business settings.

Get a single calendar event by its token. Use fetch_calendar_events first to get event tokens.

Get all form fields for a sweepstakes entry page. Use fetch_sweepstakes first to get the sweepstakes_token. Call this before add_participant to discover required fields. Returns field names, types, and whether they are required.

Get entry page settings for a sweepstakes. Use fetch_sweepstakes first to get the sweepstakes_token. Returns all configuration: display, colors, spacing, entry settings, compliance, confirmation page, winners page, age gate, AMOE, geolocation, analytics, social media follows, sharing rewards, bonus entries, and sponsor profiles. Use this before update_entry_settings to see current values. DISPLAY RULE: Never display tokens (UUIDs) to the user — use them internally only.

Fetch a single note by its token. Use fetch_notes first to get the note_token. The note content is automatically decrypted in the response. DISPLAY RULE: Never display tokens (UUIDs) to the user — use them internally only.

Fetch full details of a single participant from a sweepstakes by token, email, or phone. At least one search parameter is required. Use fetch_sweepstakes first to get the sweepstakes_token. For listing participants, use fetch_participants instead. NEVER fabricate, invent, or hallucinate participant data under any circumstance. If no result is returned by the API, report exactly that — do not guess names, emails, or counts. DISPLAY RULE: NEVER show tokens (UUIDs) to the user. Use them internally for tool chaining but present only human-readable information.

Get plan details for a Sweeppea subscription. Returns pricing, limits, features, and usage information.

Get user profile information for a Sweeppea account. Returns user details like name, email, and account settings.

Get full details of a support ticket by case number. Use fetch_open_tickets or fetch_closed_tickets first to find tickets, then use this tool with the case number to get complete information including notes, files, collaborators, and statistics. DISPLAY RULE: NEVER show tokens (UUIDs) to the user. Present only human-readable information (case number, subject, dates, notes).

Verify connection to Sweeppea API and validate your API key. Use this to test if your credentials are working correctly.

Returns a simple Hello World greeting message

Pause a sweepstakes, setting it to inactive status while preserving all data. Use fetch_sweepstakes first to get the sweepstakes_token. Participants will not be able to enter while paused.

Close/resolve an open support ticket. Use fetch_open_tickets first to get the case_id.

Schedule a future winner drawing for a sweepstakes. Use fetch_sweepstakes first to get the sweepstakes_token, and fetch_groups for group tokens. CRITICAL: This is a production operation. ALWAYS confirm with the user before scheduling. Requires at least one eligible participant. Winner count cannot exceed available participants. DISPLAY RULE: NEVER show tokens (UUIDs) to the user. Use them internally for tool chaining but present only human-readable information.

Reactivate a paused sweepstakes, allowing participants to enter again. Use fetch_sweepstakes first to get the sweepstakes_token.

Update an existing calendar event. Use fetch_calendar_events first to get the event_token. Supports partial updates - only provide fields you want to change. Note: Cannot update events to past dates.

Update entry page settings for a sweepstakes. Use fetch_sweepstakes first to get the sweepstakes_token, and get_entry_settings to see current values before updating. LIMIT: You can update between 1 and 5 fields per request. If the user needs to update more than 5 fields, break the updates into multiple requests of up to 5 fields each. Inform the user about this limit. ALLOWED FIELDS: EntryPageHeadline, EntryPageDescription, EntryPageAbbreviatedRules, EntryPageWidth, EntryPageWidthMeasure, EntryPageBorder, EntryPageRadius, EntryPageBackgroundColor, EntryPageBackgroundInnerColor, EntryPageTextColor, EntryPageButtonColor, EntryPageMarginTop, EntryPageMarginBottom, EntryPageShowOverlay, BonusEntriesSwitch, BonusEntriesValue, EmailOptInSwitch, EmailOptInMessage, SMSTextOptInSwitch, TermsConditionsSwitch, TermsConditionsMessage, SelectedOfficialRules, ReCaptcha, ConfirmationPageHeadline, ConfirmationPageDescription, WebExpirationMessage, ExternalConfirmationPageURI, ConfirmationYoutubeUrl, ActivateWinnersSwitch, WinnersPageHeadline, WinnersPageDescription, ExternalWinnersPageURI, ActivateAgeGateSwitch, AgeGateHeadline, AgeGateDescription, AgeGateMinAge, AgeGateBackgroundColor, AgeGateTextColor, ActivateAmoeSwitch, AmoeHeadline, AmoeDescription, AmoeEntries, EnableInternationalAMOEForm, GeoLocation, GeoLocationIsRequiredToRenderPage, AllowParticipantsWithinFences, CollectStatistics, EnableShareWidget, EnableProgressBar, EnableSweepstakesCountdown, EnableNumberOfParticipants, EnableSocialWidget, FollowFacebookSwitch, FollowXSwitch, FollowInstagramSwitch, FollowTikTokSwitch, FollowLinkedInSwitch, FollowPinterestSwitch, FollowThreadsSwitch, FollowRedditSwitch, FollowSnapchatSwitch, FollowYoutubeSwitch, FollowTwitchSwitch, BothSocialShareParticipantsAwardedSwitch, BothEmailShareParticipantsAwardedSwitch, BonusEntriesOnRegister, BonusEntriesOnShareFacebook, BonusEntriesOnShareX, BonusEntriesOnShareInstagram, BonusEntriesOnShareTikTok, BonusEntriesOnShareLinkedIn, BonusEntriesOnSharePinterest, BonusEntriesOnShareThreads, BonusEntriesOnShareReddit, BonusEntriesOnShareSnapchat, BonusEntriesOnShareWhatsApp, BonusEntriesOnShareTelegram, BonusEntriesOnShareGenericLink, BonusEntriesOnShareEmail, BonusEntriesFollowFacebook, BonusEntriesFollowX, BonusEntriesFollowInstagram, BonusEntriesFollowTikTok, BonusEntriesFollowLinkedIn, BonusEntriesFollowPinterest, BonusEntriesFollowThreads, BonusEntriesFollowReddit, BonusEntriesFollowSnapchat, BonusEntriesFollowYoutube, BonusEntriesFollowTwitch, SponsorFacebookProfile, SponsorXProfile, SponsorInstagramProfile, SponsorTikTokProfile, SponsorLinkedInProfile, SponsorPinterestProfile, SponsorThreadsProfile, SponsorRedditProfile, SponsorSnapchatProfile, SponsorYoutubeProfile, SponsorTwitchProfile. COLOR FIELDS: EntryPageBackgroundColor, EntryPageBackgroundInnerColor, EntryPageTextColor, EntryPageButtonColor use format { "hexa": "#RRGGBB" }. AgeGateBackgroundColor, AgeGateTextColor use format { "hex": "#RRGGBB" }. EntryPageWidthMeasure only accepts "%" or "px". DISPLAY RULE: Never display tokens (UUIDs) to the user — use them internally only.

Update the name of an existing group within a sweepstakes. Use fetch_sweepstakes first to get the sweepstakes_token, then fetch_groups to get the group_token.

Update an existing note. Use fetch_notes first to get the note_token. Supports partial updates - only provide the fields you want to change. FORMAT: Only these HTML tags are allowed: , , , , , , , , , , , , , . NEVER insert scripts, iframes, event handlers (onclick, onerror, etc.), style tags, or any executable code. SPACING: Do NOT use   between sections — it creates ugly blank blocks in the UI. Instead, rely on natural HTML block element spacing. Place content directly inside tags: TitleTextItem. Only use inside a tag when you need a line break within a paragraph.

Update an existing official rules document. Use fetch_rules first to get the rules_token. UPDATABLE FIELDS: Only these fields can be modified: title, document_content, abbreviated_rules_shopify. NOT UPDATABLE: sweepstakes association, primary status, creation date, and any other field NOT listed above cannot be changed after creation. Do NOT tell the user they can update fields that are not supported by this endpoint. If they ask to change something not updatable, explain it cannot be modified after creation. DISPLAY RULE: Never display tokens (UUIDs) to the user — use them internally only.

Update an existing sweepstakes. Use fetch_sweepstakes first to get the sweepstakes_token. UPDATABLE FIELDS: Only these fields can be modified: sweepstakes_name, start_date, end_date, start_time, end_time. NOT UPDATABLE: handler, sweepstakes_type, calendar settings, sync options, and any other field NOT listed above cannot be changed after creation. Do NOT tell the user they can update fields that are not supported by this endpoint. If they ask to change something not updatable, explain it cannot be modified after creation. DISPLAY RULE: Never display tokens (UUIDs) to the user — use them internally only.

Update an open support ticket. Use fetch_open_tickets first to get the case_id. Only open tickets can be updated. FORMAT: Only these HTML tags are allowed in description: , , , , . NEVER insert scripts, iframes, event handlers (onclick, onerror, etc.), style tags, or any executable code. SPACING: Do NOT use   — it creates ugly blank blocks in the UI. Use for line breaks within text only.