Skip to main content
Glama

Sweeppea MCP

by com.sweeppea.mcp
OverviewDiscussionsAdmin

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. WHEN THE GATE IS ON: with ActivateAgeGateSwitch true, AgeGateMinAge must be 3 (21+) — the account validation rejects 1 and 2 while the gate is active, so the three enum values are NOT interchangeable here. The Age Gate is the 21+ control (alcohol, nicotine/vaping, cannabis); for a plain 18+ eligibility rule leave the gate off and set min_age=1 in create_rules_wizard. Always send ActivateAgeGateSwitch and AgeGateMinAge in the same request. 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

  1. 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
NameRequiredDescriptionDefault
settingsYesObject 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_tokenYesThe sweepstakes token (UUID format)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: AgeGateMinAge is an enum with 1/2/3 meanings, account validation rejects 1 and 2 while the gate is active, ReCaptcha is read-only, prize fields are not editable by any MCP tool, and color fields require different formats for EntryPage* vs AgeGate*. These are exactly the non-obvious behaviors an agent needs to avoid failed or non-compliant calls.

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 content is highly valuable but heavily duplicated: the opening paragraph, the '## When to use' section, and the 'Notes' section repeat the same field lists, color formats, and prize guardrail nearly verbatim. The structure is front-loaded and sectioned, but the redundancy bloats the description well beyond what is needed for the same informational content.

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?

For a tool with a nested settings object, no output schema, and high compliance sensitivity, the description covers pre-calls, parameter validation, field enumeration, enum semantics, color formats, request-size limits, read-only fields, and the critical prize-edit prohibition. Nothing an agent needs to call this tool correctly and avoid compliance violations is missing.

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 massively extends parameter meaning by enumerating allowed settings field names, distinguishing compliance vs display fields, explaining AgeGateMinAge enum semantics, specifying color object shapes, and providing a concrete example. This is far beyond what the bare schema gives the agent.

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 opens with a specific verb and resource: 'Update entry page settings (1-5 fields per request).' It clearly distinguishes this tool from siblings by naming get_entry_settings as the discovery pre-call and explicitly separating this tool's scope from create_rules_wizard and from any prize-editing capability. The purpose is unmistakable even before inspecting the schema.

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 when-to-use guidance: call get_entry_settings first, use fetch_sweepstakes if given a name instead of a token, split updates beyond 5 fields into multiple requests, and never use this tool for prize changes. It also names an alternative path (create_rules_wizard min_age=1 for plain 18+ eligibility) and states what to do instead for prize edits.

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

All Sweeppea MCP 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