Skip to main content
Glama
Sign In
Qualtrics MCP Server

Qualtrics MCP Server

by yrvelez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_reminder

Send a reminder for an existing email distribution, scheduling it immediately or on a specified date.

Instructions

Send a reminder for an existing email distribution

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": {
      "distributionId": "<distributionId>",
      "fromEmail": "<fromEmail>",
      "fromName": "<fromName>",
      "replyToEmail": "<replyToEmail>",
      "subject": "<subject>",
      "messageId": "<messageId>",
      "libraryId": "<libraryId>"
    },
    "name": "create_reminder"
  }
}

Input Schema

NameRequiredDescriptionDefault
subjectYesReminder email subject line
fromNameYesFrom name displayed in the reminder email
sendDateNoScheduled send date (ISO format). If omitted, sends immediately.
fromEmailYesVerified sender email address
libraryIdYesID of the library containing the message template
messageIdYesID of the reminder message template
embeddedDataNoOptional tags for distribution reporting; these are not survey-flow embedded data
replyToEmailYesReply-to email address
distributionIdYesThe parent distribution ID to send a reminder for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false, so description carries burden for additional behavioral traits. Description is minimal and does not disclose key behaviors, such as whether sending is immediate or scheduled based on sendDate, or that it creates a new reminder record. However, schema hints at scheduling, partially mitigating transparency gap.

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 clear sentence with no wasted words. It is front-loaded with the core purpose, but could be slightly longer to include usage guidance without losing conciseness.

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 9 parameters, no output schema, and nested objects, the description is too brief. It omits prerequisites (e.g., distribution must exist), behavioral details (immediate vs. scheduled), and what the response contains. Schema covers parameters but description fails to provide higher-level context.

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 descriptions cover 100% of parameters with meaningful explanations. The tool description adds no additional meaning beyond what the schema provides, so baseline score 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 'Send a reminder for an existing email distribution' clearly states the action (send) and the resource (reminder for an existing distribution). It distinguishes from siblings like create_email_distribution and create_thank_you.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., create_thank_you), no prerequisites (e.g., distribution must exist), and no exclusions. Sibling tools offer similar sending functionality but the description does not differentiate usage 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