Skip to main content
Glama

Sweeppea MCP

by com.sweeppea.mcp
OverviewDiscussionsAdmin

delete_survey

DestructiveIdempotent

Permanently delete a survey. IRREVERSIBLE — deletes the survey, its questions, ALL collected responses, stats and uploaded files. NEVER call without explicit user confirmation for this specific survey, spelling out what will be lost. confirm=true is REQUIRED for every call and is also what the API demands when the survey already has responses — set it only after the user explicitly accepted losing them. Participants created from the survey and the sweepstakes itself are preserved. To disable a survey WITHOUT losing data, use update_survey with status false instead — always offer that alternative first. Requires the Surveys module enabled — on 403 "module is not enabled", do NOT retry; tell the user to contact Sweeppea support.

delete_survey

When to use

Permanently delete a survey. IRREVERSIBLE — deletes the survey, its questions, ALL collected responses, stats and uploaded files. NEVER call without explicit user confirmation for this specific survey, spelling out what will be lost. If the survey has responses the API additionally requires confirm=true (409 otherwise) — only pass confirm=true after the user explicitly accepted losing the responses. Participants created from the survey and the sweepstakes itself are preserved. To disable a survey WITHOUT losing data, use update_survey with status false instead — always offer that alternative first. Requires the Surveys module enabled — on 403 "module is not enabled", do NOT retry; tell the user to contact Sweeppea support.

Pre-calls required

  1. get_survey — check ResponsesCount and tell the user exactly what will be lost

Parameters to validate before calling

  • survey_token (string, required) — The survey token (UUID v4) of the survey to delete

  • confirm (boolean, optional) — Required true ONLY when the survey already has responses. Pass it ONLY after the user explicitly confirmed losing all responses

Notes

  • DESTRUCTIVE — IRREVERSIBLE. Always confirm with the user before calling. Explain what will be lost.

  • Deletes questions, ALL responses, stats and uploaded files. Participants created from the survey are preserved

  • confirm: true is required when responses exist — pass it ONLY after the user explicitly accepted losing them

  • Offer update_survey with status false first (disable without data loss)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmYesMust be true. Set it ONLY after the user explicitly confirmed THIS deletion in this conversation, having been told what is lost: the survey, its questions, ALL collected responses, stats and uploaded files. Never assume, never carry a confirmation over from a previous item, never set it to satisfy the schema.
survey_tokenYesThe survey token (UUID v4) of the survey to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / confirm / description
      Previous value: -"Required true ONLY when the survey already has responses. Pass it ONLY after the user explicitly confirmed losing all responses"New value: +"Must be true. Set it ONLY after the user explicitly confirmed THIS deletion in this conversation, having been told what is lost: the survey, its questions, ALL collected responses, stats and uploaded files. Never assume, never carry a confirmation over from a previous item, never set it to satisfy the schema."
    • changedInput schema / required
      Previous value: -[
-  "survey_token"
-]New value: +[
+  "survey_token",
+  "confirm"
+]
  2. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already mark destructiveHint=true and readOnlyHint=false; the description adds valuable specifics (deletes questions/responses/stats/files, preserves participants and sweepstakes, 409/403 handling). However, it contradicts itself on confirm: first says 'confirm=true is REQUIRED for every call,' later says it is 'optional' and only needed when responses exist. This inconsistency undermines behavioral clarity.

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 same warnings (irreversible, confirm after explicit acceptance, update_survey alternative, preserved participants) are repeated almost verbatim across the opening paragraph, 'When to use,' 'Parameters,' and 'Notes.' Although headings and front-loading help, the redundancy is excessive and should be consolidated.

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

Completeness3/5

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

The description covers pre-calls, parameter validation, error handling, and alternatives, so it is nearly complete for a destructive tool. It is not fully reliable because the confirm requirement is stated inconsistently, leaving the agent unsure whether confirm is mandatory on every call or only when responses exist.

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

Parameters2/5

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

Schema already documents both parameters at 100% coverage. The description adds important context about user confirmation and 409 behavior, but it mislabels confirm as '(boolean, optional)' even though the schema lists it as required, and it contradicts the opening claim that confirm=true is required for every call. That makes the parameter guidance actively misleading.

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?

Opens with 'Permanently delete a survey' — a specific verb, resource, and scope — and enumerates exactly what is destroyed (questions, responses, stats, uploaded files) and what survives (participants, sweepstakes). It also distinguishes itself from update_survey, so an agent can pick the right sibling.

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?

Explicit 'When to use' section plus a clear exclusion: 'To disable a survey WITHOUT losing data, use update_survey with status false instead — always offer that alternative first.' It also mandates a get_survey pre-call to inspect ResponsesCount and warns not to retry on 403. This is model usage guidance.

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