Skip to main content
Glama
Sign In
Qualtrics MCP Server

Qualtrics MCP Server

by yrvelez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_distribution_links

Retrieve a paginated list of individual survey links for a specified distribution and survey. Use the skipToken from a prior page to navigate through results.

Instructions

List one page of generated individual survey links. WARNING: Qualtrics documents that this GET can update contact-frequency state and reset email-status dates when used on other distribution types, so the distributions write scope is required.

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": {
      "distributionId": "<distributionId>",
      "surveyId": "<surveyId>"
    },
    "name": "list_distribution_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
surveyIdYesThe Qualtrics survey ID
skipTokenNoOpaque token from the prior page's nextPage value
distributionIdYesThe distribution ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior5/5

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

The description explicitly discloses beyond annotations that this GET can update contact-frequency state and reset email-status dates, providing critical behavioral context that annotations (readOnlyHint=false, destructiveHint=false) only hint at.

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 the core purpose, and a critical warning. No unnecessary words.

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?

While parameters are well documented in schema, the description does not elaborate on the output structure (e.g., format of links, pagination details). For a tool without output schema, more context would 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 all parameters described, so the description adds no extra meaning beyond the schema. Baseline 3 is appropriate.

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 'List one page of generated individual survey links', specifying the verb (list), resource (individual survey links), and pagination (one page). It distinguishes from siblings like list_distributions which list distributions, not links.

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?

The description warns of side effects and required scope, implying caution and suggesting when not to use (if avoiding state changes), but does not explicitly name alternative tools like list_distributions for read-only distribution listing.

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