Skip to main content
Glama
Sign In
Qualtrics MCP Server

Qualtrics MCP Server

by yrvelez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_mailing_lists

Read-only

List mailing lists from a Qualtrics XM Directory by directory ID, with support for pagination, owner filtering, and optional contact counts.

Instructions

List one cursor-paginated page of mailing lists in an XM Directory

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": {
      "directoryId": "<directoryId>"
    },
    "name": "list_mailing_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerIdNoXM Directory owner or group ID used to include shared mailing lists
pageSizeNoXM Directory page size (maximum 100)
skipTokenNoXM Directory pagination token from nextSkipToken
directoryIdYesRequired XM Directory ID (POOL_...), also known as the directory or pool ID
includeCountNoAsk XM Directory to calculate approximate contact counts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds value by specifying that it returns 'one cursor-paginated page', disclosing the pagination behavior beyond the schema. However, it does not elaborate on error conditions or rate limits.

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 sentence that conveys the essential information without redundant or extraneous words. It is well-structured and front-loaded.

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?

Given the absence of an output schema, the description could have explained the return structure (e.g., list of mailing list objects with pagination token). However, the high schema coverage and annotation compensate somewhat, leaving it minimally adequate but not fully 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?

All 5 parameters have descriptions in the input schema (100% coverage), so the description adds no additional semantic value for individual parameters. The baseline of 3 is appropriate as the description does not compensate with parameter-specific details.

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 ('List'), resource ('mailing lists'), scope ('in an XM Directory'), and includes the pagination detail ('one cursor-paginated page'). This distinguishes it from sibling tools like get_mailing_list or list_directories.

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 implies usage for listing mailing lists but provides no explicit guidance on when to use this tool versus alternatives (e.g., get_mailing_list for a specific list). No when-not-to or prerequisite conditions are mentioned.

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