Skip to main content
Glama
Sign In
Qualtrics MCP Server

Qualtrics MCP Server

by yrvelez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_mailing_list

Destructive

Permanently remove a mailing list from a Qualtrics XM directory by providing the directory ID, mailing list ID, and confirmation.

Instructions

Delete a mailing list

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>",
      "mailingListId": "<mailingListId>",
      "confirmDelete": "<confirmDelete>"
    },
    "name": "delete_mailing_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
directoryIdYesRequired XM Directory ID (POOL_...), also known as the directory or pool ID
confirmDeleteYesMust be true to confirm deletion
mailingListIdYesThe mailing list ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

Only states 'Delete', consistent with destructiveHint=true, but lacks details on consequences, reversibility, or required permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no wasted words, but underspecified for a destructive action.

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 the tool's destructive nature and lack of output schema, the description fails to provide necessary context like effects on related data or recovery options.

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 covers all parameters with descriptions (100% coverage), so description adds no extra meaning beyond what's already there.

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?

Clear verb ('Delete') and resource ('mailing list'), distinct from sibling tools like delete_survey or delete_question.

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?

No guidance on when to use or when to avoid, no mention of prerequisites or alternatives.

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