Skip to main content
Glama
Sign In
Qualtrics MCP Server

Qualtrics MCP Server

by yrvelez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

add_text_entry_question

Add a text entry question to a survey block, choosing between single line, multi line, and essay formats.

Instructions

Simplified helper to create a text entry question (single line, multi line, or essay).

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>",
      "blockId": "<blockId>",
      "questionText": "<questionText>",
      "textType": "<textType>"
    },
    "name": "add_text_entry_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
blockIdYesThe block ID to add the question to
surveyIdYesThe Qualtrics survey ID
textTypeYesText entry type: single line, multi line, or essay
questionTextYesThe question text
dataExportTagNoMeaningful export tag; derived uniquely from questionText if omitted
forceResponseNoRequire a response (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

The description provides minimal behavioral context beyond annotations. 'Simplified helper' implies easier use but doesn't disclose any side effects, validation, or required permissions. Since annotations only indicate non-destructive, more transparency is needed for a creation tool.

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?

The description is a single, efficient sentence that is front-loaded with the core purpose. However, it could include more detail without becoming overly long.

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

Completeness2/5

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

Given no output schema and moderate complexity (6 params, 4 required), the description is too brief. It does not explain return values, side effects, or how it differs from the generic create_question tool. Sibling tools include many other question types, so more context would help.

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 baseline is 3. The description does not add any additional meaning beyond what the schema already provides for parameters. It simply repeats the resource type.

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 action ('create') and the specific resource ('text entry question') with explicit types (single line, multi line, or essay). It distinguishes this tool from sibling tools like add_multiple_choice_question, add_likert_question, etc.

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

Usage Guidelines2/5

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

The description lacks guidance on when to use this tool versus alternatives, no exclusions, no prerequisites. It only mentions 'Simplified helper' but does not elaborate on contexts where it is preferred over other question-creation 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