Skip to main content
Glama
Sign In
Qualtrics MCP Server

Qualtrics MCP Server

by yrvelez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_surveys

Read-only

Retrieve a page of surveys from your Qualtrics account, with optional filtering by name and pagination support using nextPage offset.

Instructions

List one Qualtrics-managed page of surveys with optional name filtering; use nextPage to continue

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_surveys"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoFilter this returned page by name (case-insensitive partial match)
offsetNoStarting offset for pagination (default: 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description confirms read-only behavior with 'List'. It adds pagination detail (nextPage) beyond annotations, which is useful behavioral context.

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?

The description is a single, front-loaded sentence that efficiently conveys the core purpose and a key detail (pagination). No redundant or unnecessary 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?

The description covers the core listing functionality and pagination hint, but lacks details on return format (e.g., survey objects) or how to use nextPage exactly. Given the low complexity and rich schema, it is mostly complete.

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?

The input schema already describes both parameters with 100% coverage. The description adds minimal semantic value ('optional name filtering' matches filter parameter) but doesn't exceed what the schema provides.

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 'List one Qualtrics-managed page of surveys' uses a specific verb and resource, clearly states the scope (one page), and distinguishes from sibling tools like create_survey or delete_survey by focusing on listing.

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?

The description implies pagination via 'use nextPage to continue', but does not explicitly state when to use this tool vs alternatives (e.g., search for surveys by name). However, context signals show many sibling tools are for create, update, delete, making the purpose clear.

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