Skip to main content
Glama
Sign In
Qualtrics MCP Server

Qualtrics MCP Server

by yrvelez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

update_survey_languages

Idempotent

Update available languages for a Qualtrics survey by merging or replacing the language map.

Instructions

Update the survey's AvailableLanguages option map through the documented survey-options PUT. The complete current options resource is fetched and preserved. By default language-map keys are merged; set replace=true to replace the complete AvailableLanguages map. Requires Translate Surveys permission.

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": {
      "surveyId": "<surveyId>",
      "availableLanguages": "<availableLanguages>"
    },
    "name": "update_survey_languages"
  }
}

Input Schema

NameRequiredDescriptionDefault
replaceNoReplace rather than merge the AvailableLanguages map (default: false)
surveyIdYesThe Qualtrics survey ID
availableLanguagesYesAvailableLanguages option-map patch keyed by language code, or the complete map when replace=true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Adds important behavioral details beyond annotations: explains that the complete current options resource is fetched and preserved, and that keys are merged by default. No contradiction with idempotent and non-destructive hints.

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?

Three succinct sentences covering purpose, mechanism, behavior, and permission. No redundancy or unnecessary details.

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?

Comprehensive for a mutation tool, though missing explicit return value (output schema absent). Still sufficiently complete for an agent to use correctly.

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?

Adds value to the already well-described schema by explaining the availableLanguages parameter as a 'patch keyed by language code' and clarifying the replace parameter's effect on merging vs. replacement.

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 clearly states the tool updates the AvailableLanguages option map via PUT, specifying the mechanism (fetches and preserves current options) and distinguishing from siblings like get_survey_languages or update_survey.

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?

Explicitly mentions required permission ('Requires Translate Surveys permission') and describes default merge behavior with option to replace, but could improve by stating when not to use or listing alternatives.

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

Deploy Server

Other Tools