Sweeppea MCP

update_entry_settings

Idempotent

Update entry page settings (1-5 fields per request). Call get_entry_settings first to see all available field names and current values. COMPLIANCE FIELDS: TermsConditionsSwitch, TermsConditionsMessage, SelectedOfficialRules, ActivateAgeGateSwitch, AgeGateHeadline, AgeGateDescription, AgeGateMinAge, ActivateAmoeSwitch, AmoeHeadline, AmoeDescription, AmoeEntries, EnableInternationalAMOEForm, GeoLocation, GeoLocationIsRequiredToRenderPage, AllowParticipantsWithinFences. DISPLAY FIELDS: EntryPageHeadline, EntryPageDescription, EntryPageWidth, EntryPageWidthMeasure ("%" or "px"), EntryPageBorder, EntryPageRadius, BonusEntriesSwitch, EmailOptInSwitch, SMSTextOptInSwitch. For social follows, bonus entries per platform, sponsor profiles, and other fields: call get_entry_settings to discover names. AGE GATE VALUE: AgeGateMinAge is an ENUM, not an age in years — 1 = 13 years or older, 2 = 18 years or older, 3 = 21 years or older. Sending 13, 18 or 21 is rejected by the API. For alcohol/cannabis promotions (21+) send AgeGateMinAge: 3. Do NOT confuse it with the create_rules_wizard min_age enum, which uses different codes (1 = 18+, 2 = 21+, 3 = 13+). COLOR FORMAT: EntryPageColor fields use {"hexa":"#RRGGBB"}. AgeGateColor fields use {"hex":"#RRGGBB"}. All field names are PascalCase. If more than 5 fields need updating, split into multiple requests. NOTE: ReCaptcha is read-only — not writable via this endpoint. PRIZE GUARDRAIL: The prize value/description of a sweepstakes is NOT editable via this tool or any other MCP tool. NEVER simulate a prize change by writing a new amount into EntryPageHeadline, EntryPageDescription, or any other display text — that makes the entry page contradict the Official Rules and internal records (a compliance violation). If the user asks to change the prize, explain it cannot be modified after creation and direct them to Sweeppea support.

update_entry_settings

When to use

Update entry page settings (1-5 fields per request). Call get_entry_settings first to see all available field names and current values. COMPLIANCE FIELDS: TermsConditionsSwitch, TermsConditionsMessage, SelectedOfficialRules, ActivateAgeGateSwitch, AgeGateHeadline, AgeGateDescription, AgeGateMinAge, ActivateAmoeSwitch, AmoeHeadline, AmoeDescription, AmoeEntries, EnableInternationalAMOEForm, GeoLocation, GeoLocationIsRequiredToRenderPage, AllowParticipantsWithinFences. DISPLAY FIELDS: EntryPageHeadline, EntryPageDescription, EntryPageWidth, EntryPageWidthMeasure ("%" or "px"), EntryPageBorder, EntryPageRadius, BonusEntriesSwitch, EmailOptInSwitch, SMSTextOptInSwitch. For social follows, bonus entries per platform, sponsor profiles, and other fields: call get_entry_settings to discover names. COLOR FORMAT: EntryPageColor fields use {"hexa":"#RRGGBB"}. AgeGateColor fields use {"hex":"#RRGGBB"}. All field names are PascalCase. If more than 5 fields need updating, split into multiple requests. NOTE: ReCaptcha is read-only — not writable via this endpoint. PRIZE GUARDRAIL: The prize value/description of a sweepstakes is NOT editable via this tool or any other MCP tool. NEVER simulate a prize change by writing a new amount into EntryPageHeadline, EntryPageDescription, or any other display text — that makes the entry page contradict the Official Rules and internal records (a compliance violation). If the user asks to change the prize, explain it cannot be modified after creation and direct them to Sweeppea support.

Pre-calls required

fetch_sweepstakes if the user gave you a sweepstakes name instead of a token

Parameters to validate before calling

sweepstakes_token (string, required) — The sweepstakes token (UUID format)
settings (object, required) — Object with 1 to 5 settings fields to update. Field names must be PascalCase as listed in the tool description. Example: { "EntryPageHeadline": "Win Big!", "BonusEntriesSwitch": true }

Notes

Maximum 5 fields per request — split larger updates into multiple calls
Top-level fields are PascalCase (e.g. TermsConditionsSwitch, ActivateAmoeSwitch)
Color fields use {"hexa": "#RRGGBB"} format
TermsConditionsSwitch MUST be true for legal compliance
Age Gate is exclusively for 21+ promotions (alcohol, cannabis) — never enable for 13/18
Prize value/description is NOT editable via MCP — NEVER simulate a prize change by writing amounts into EntryPageHeadline/EntryPageDescription; direct the user to Sweeppea support

Input Schema

TableJSON Schema

Name	Required	Description	Default
`settings`	Yes	Object with 1 to 5 settings fields to update. Field names must be PascalCase as listed in the tool description. Example: { "EntryPageHeadline": "Win Big!", "BonusEntriesSwitch": true }
`sweepstakes_token`	Yes	The sweepstakes token (UUID format)

TDQS

A4.7/5.0

Behavior5/5

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

The annotations already indicate a non-read-only, idempotent, non-destructive tool, and the description adds substantial behavioral context: the 5-field limit, AgeGateMinAge enum quirks, color format differences, read-only ReCaptcha, and the critical prize guardrail. There is no contradiction with the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is heavily redundant: the compliance/display field lists, color formats, 5-field limit, and prize guardrail are repeated nearly verbatim in both the top paragraph and the later markdown sections. The structure helps scanning, but the duplicate content violates the 'every sentence earns its place' principle.

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?

Given the tool's complexity, nested settings object, enumerated fields, and compliance risks, the description is remarkably complete. It covers pre-calls, field-name discovery, validation constraints, unsupported operations, and safety rules, leaving little ambiguity for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description goes far beyond the schema by enumerating valid field names, requiring PascalCase, explaining the AgeGateMinAge enum values, specifying color object formats, and providing a concrete example. This is high-value semantic detail that the schema alone does not convey.

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 description states exactly what the tool does: 'Update entry page settings (1-5 fields per request).' It clearly identifies the resource and key constraints, and it distinguishes itself from read-oriented siblings like get_entry_settings by making the update intent explicit.

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?

The description gives explicit guidance: 'Call get_entry_settings first,' 'If more than 5 fields need updating, split into multiple requests,' and a 'Pre-calls required' section explaining fetch_sweepstakes. It also tells the agent when NOT to use the tool, such as for prize changes, and directs the user to Sweeppea support.

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

All Sweeppea MCP tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation4/5

Most tools follow a clear resource+action pattern (fetch_* for lists, get_* for single items, create/update/delete for writes), making them distinguishable. A few near-overlaps exist (fetch_billing_transactions vs fetch_wallet_transactions, draw_winners vs schedule_drawing) but the descriptions clarify the boundaries.

Naming Consistency4/5

Tool names consistently use snake_case verb_noun, with fetch_ for list operations and get_ for single-item retrieval. Some verb variation (add_participant, count_participants, draw_winners, schedule_drawing) deviates from the dominant create/fetch/update/delete pattern but remains predictable and readable.

Tool Count1/5

With 83 tools, this is far beyond a well-scoped server (typically 3-15, with 25+ considered too many). Even though the platform has broad functionality, the sheer number of tools creates significant agent confusion and selection overhead.

Completeness4/5

The sweepstakes domain is thoroughly covered: lifecycle management, participants, groups, rules, drawings, winners, calendar, notes, todos, tickets, surveys, invoices, billing, files, and entry settings. A few minor gaps exist (e.g., no general participant field update, no archive action) but the surface is remarkably complete for its scope.

Resources

Need Help?