Skip to main content
Glama
Sign In
Qualtrics MCP Server

Qualtrics MCP Server

by yrvelez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

remove_contact

Destructive

Remove a contact from a mailing list while retaining the contact in the XM Directory. Requires confirmation to delete.

Instructions

Remove a contact from this mailing list only; the contact remains in the 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>",
      "mailingListId": "<mailingListId>",
      "contactId": "<contactId>",
      "confirmDelete": "<confirmDelete>"
    },
    "name": "remove_contact"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark destructiveHint=true. The description adds that only the mailing list membership is removed, not the contact itself, which is key behavioral context not covered by annotations. However, it does not mention the confirmDelete safety mechanism.

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?

Single sentence conveying the action and scope with no redundancy. Efficient and front-loaded.

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?

For a simple removal tool with no output schema, the description adequately explains the scope of the removal. It could mention the confirmDelete requirement, but that is already in the schema. Overall sufficient.

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 description does not need to add parameter details. The tool description does not expand on individual parameters beyond what the schema already provides, meeting the baseline.

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?

Description clearly states the tool removes a contact from a mailing list only, and specifies the contact remains in the XM Directory. This distinguishes it from a full delete and aligns with its purpose among sibling tools like add_contact and update_contact.

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 the tool is for removal from a list without directory deletion, but it does not explicitly state when to use this versus alternatives or provide exclusions. No explicit guidance on prerequisites or context.

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