Skip to main content
Glama
Sign In
Qualtrics MCP Server

Qualtrics MCP Server

by yrvelez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

update_contact

Idempotent

Update an existing contact's information in a Qualtrics mailing list, including email, phone, name, language, embedded data, and subscription status. Provide directory ID, mailing list ID, and contact ID.

Instructions

Update an existing contact in 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>",
      "contactId": "<contactId>"
    },
    "name": "update_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoUpdated email address
phoneNoUpdated phone number
languageNoUpdated language code
lastNameNoUpdated last name
contactIdYesThe contact ID to update
firstNameNoUpdated first name
directoryIdYesRequired XM Directory ID (POOL_...), also known as the directory or pool ID
embeddedDataNoUpdated embedded data fields
unsubscribedNoUpdated unsubscribe state
mailingListIdYesThe mailing list ID
externalDataReferenceNoUpdated external reference (extRef)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false. Description adds no additional behavioral context beyond 'Update', such as whether missing contacts cause errors or if partial updates are supported. Bar is lowered by annotations, but description doesn't enrich transparency.

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

Conciseness4/5

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

The description is a single concise sentence with no wasted words. It clearly states the action and object. However, it could be slightly expanded to include more context without losing brevity.

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?

For a tool with 11 parameters, nested objects, and no output schema, the description is insufficient. It lacks details on response behavior, required context (e.g., directoryId meaning), and how the update interacts with mailing lists. Agent would struggle to use it effectively without additional information.

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 descriptions for all 11 parameters. The tool description adds no parameter-level meaning beyond what the schema already provides. Baseline of 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 it updates an existing contact in a mailing list. It uses a specific verb ('update') and resource ('contact in a mailing list'), and is distinct from sibling tools like add_contact, remove_contact, or list_contacts.

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 updating an existing contact, but gives no explicit guidance on when to use this tool versus alternatives (e.g., add_contact for new contacts, remove_contact for deletion). No prerequisites or when-not-to-use information is provided.

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