Skip to main content
Glama

delete_responses

DestructiveIdempotent

Permanently delete survey responses with confirm: true: the ones listed (scope selected), only recruitment test-link responses (scope test_link), or every response (scope all). Cannot be undone.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "survey_id": "<survey_id>",
      "scope": "<scope>",
      "confirm": "<confirm>"
    },
    "name": "delete_responses"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeYesWhich responses to delete: selected (the ids in response_ids), test_link (only responses made through a recruitment provider's test link, labeled as tests), or all (every response in the survey). There is no default, so all is never implied.
confirmYesMust be true. Deletion is permanent and cannot be undone from survey trash.
survey_idYesSurvey UUID
response_idsNoRequired with scope selected: the response ids to delete (from read_responses).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the description's added value is the explicit "Cannot be undone" wording plus the mandatory confirm gate, which raises the bar for accidental invocation. It stops short of detailing what happens to linked/unfinished responses or the returned payload, but the with-annotations bar is lower and the key irreversible behavior is disclosed.

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

Conciseness5/5

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

A single front-loaded sentence leads with the action and permanence, then presents the three scopes as a compact parallel list. No filler sentences, and the most safety-critical clause ("Cannot be undone") is the closing emphasis.

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

Completeness4/5

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

With an output schema present, return values need no explanation, and the description covers the destructive nature, the confirm gate, and all scope variants. It only lightly implies that response_ids is required alongside scope=selected, but the schema fills that gap. Adequate for a 4-parameter destructive tool.

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

Parameters3/5

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

Schema description coverage is 100%, so the enum meanings for scope and the confirm requirement are already fully documented in the schema. The description restates those enum values and the confirm flag rather than adding syntax, ordering, or constraint detail beyond what structured data provides; baseline 3 applies.

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?

States a specific verb and resource ("Permanently delete survey responses") and immediately enumerates the three deletion scopes, so an agent knows exactly what the tool does and how the scope changes the effect. It is clearly distinguishable from edit_responses/read_responses by the word "delete" and the permanence statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains when each scope applies (selected = the listed ids, test_link = recruitment test-link responses, all = every response) and states the precondition that confirm must be true. It does not explicitly route the agent away from edit_responses or read_responses when only modification or inspection is wanted, which keeps it short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources