Skip to main content
Glama
Sign In
Qualtrics MCP Server

Qualtrics MCP Server

by yrvelez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

import_survey_from_url

Import a survey from a publicly accessible URL in QSF, TXT, or DOCX format. Qualtrics fetches the file, enabling survey creation without manual upload.

Instructions

Create a survey from a publicly accessible QSF, TXT, or DOCX URL. Qualtrics fetches the file, so private/local URLs will not work.

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": {
      "name": "<name>",
      "format": "<format>",
      "fileUrl": "<fileUrl>"
    },
    "name": "import_survey_from_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName for the imported survey
formatYesFile format
fileUrlYesPublic HTTPS URL of the import file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

Annotations only provide destructiveHint: false. The description adds that Qualtrics fetches the file and that private URLs don't work, but doesn't disclose other behaviors like return value, permissions, or side effects.

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?

Two-sentence description that is front-loaded with the core action and quickly addresses key constraint. No wasted words.

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 the presence of sibling import tools and full schema coverage, the description covers the essential constraints. However, lacking output schema, it does not describe the return value, which could be helpful.

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 coverage is 100% with descriptions for all three parameters (name, format, fileUrl). The description adds only the clarification about public URLs, which is partially redundant with the fileUrl parameter description indicating a 'Public HTTPS URL'.

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?

Clearly states the action (create a survey), the resource (survey), and the allowed input formats (publicly accessible QSF, TXT, or DOCX URL). Distinguishes from sibling import tools that may accept direct file uploads.

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 notes that the URL must be publicly accessible and that private/local URLs won't work. This helps agents understand constraints, though it doesn't explicitly mention when to use alternative import tools.

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