Skip to main content
Glama
yrvelez

Qualtrics MCP Server

by yrvelez

add_web_service

Add a Web Service call to a Qualtrics survey flow and map JSON response values to embedded data fields for piped text.

Instructions

Add a Web Service element anywhere in the survey flow. Response values can be mapped to embedded data fields for downstream piped text. For authentication, headers, or advanced Qualtrics fields, use additionalFields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesTarget URL for the HTTP call (can include piped text like ${e://Field/ResponseID})
methodNoHTTP method (default: GET)
surveyIdYesThe Qualtrics survey ID
placementNoInsertion position (default: beginning)
requestParamsNoRequest parameters sent as the body (for POST/PUT) or query string (for GET)
referenceFlowIdNoRequired for before, after, inside_beginning, and inside_end
responseMappingYesMap response JSON paths to embedded data fields
additionalFieldsNoOther WebService definition fields, such as headers or authentication; merged last
declareResponseFieldsNoAlso insert an EmbeddedData declaration for mapped fields (default: true)
Behavior2/5

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

Annotations only provide destructiveHint: false, so the description carries full burden. It does not disclose permissions, reversibility, failure behavior, or side effects beyond creation. For a mutation tool, this is insufficient.

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 sentences, front-loaded with core action, no redundant information. Every sentence adds value.

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?

Covers core purpose and key parameters like responseMapping and additionalFields. However, lacks explanation for return values, required parameter referenceFlowId, and overall flow impact. Given complexity and no output schema, more context would help.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. The description adds value by explaining responseMapping for piped text and additionalFields for advanced options, but other parameters (url, method, placement) are not further detailed.

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 it adds a Web Service element in the survey flow, and distinguishes from siblings like list_web_services and add_embedded_data by specifying the resource and purpose.

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?

It gives context for using additionalFields for authentication/headers, but does not explicitly state when to use alternatives (e.g., add_embedded_data) or when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yrvelez/qualtrics-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server