Skip to main content
Glama

edit_responses

Set per-response quality review decisions, or save the survey's remembered export privacy choices (Export tab or replication packages). Use delete_responses to remove response rows.

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>"
    },
    "name": "edit_responses"
  }
}

Input Schema

NameRequiredDescriptionDefault
survey_idYesSurvey UUID
export_privacyNoSave this survey's remembered privacy choices for one place, replacing what was saved there — the same choices the Export tab and deposit dialogs remember. Needs edit access. The team's export privacy minimum still applies on top when exporting.
quality_reviewNoSet the Data quality review for one response — the same decision, tags, and note as the Responses review panel. The whole review is replaced, not merged.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Adds real context beyond the annotations: edit access is required, the team's export privacy minimum still applies on top at export time, and both modes replace rather than merge saved state (omitting tags/notes clears them). The replace semantics sit slightly awkwardly against idempotentHint=false, but this is a nuance rather than a direct contradiction.

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

Conciseness4/5

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

Two sentences, front-loaded with the two capabilities and ending with the sibling exclusion. Dense but no wasted words; the only cost is that cramming two unrelated operations into one sentence makes the mode split slightly harder to parse.

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?

Given an output schema, rich annotations, and a fully documented input schema, the description covers what remains: the two modes, access requirements, replace-not-merge behavior, and the export-time privacy floor. Only the mode-selection mapping is left implicit.

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% and the schema is extremely detailed, documenting enums, defaults, and per-column treatment rules. The description adds no parameter-level meaning beyond what the schema already provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States two specific verbs and resources: setting per-response quality review decisions and saving the survey's remembered export privacy choices. It also names the sibling it is not (delete_responses). The dual-mode nature is clear from the text, though it never says which parameter selects which mode, leaving that to 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 Guidelines3/5

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

Explicitly routes row removal to delete_responses, which is useful. However, it gives no guidance on when to use the quality_review mode versus the export_privacy mode, nor any prerequisites beyond 'Needs edit access' buried in the export_privacy schema description.

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