Skip to main content
Glama
Sign In
Qualtrics MCP Server

Qualtrics MCP Server

by yrvelez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_library_blocks

Read-only

Lists reusable survey blocks from a Qualtrics library to help you discover and copy block definitions for your surveys.

Instructions

List reusable survey blocks in a Qualtrics library. Use these templates to discover complex block definitions before copying or recreating them through MCP.

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": {
      "libraryId": "<libraryId>"
    },
    "name": "list_library_blocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNoPagination offset
libraryIdYesThe library 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 declare readOnlyHint=true. Description adds context that blocks are 'templates' for 'copying or recreating', implying no side effects and providing usage intent beyond the annotation.

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?

Two concise sentences with no fluff. First sentence states action and resource; second adds purpose. Every sentence earns its place.

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 list tool with 2 parameters and no output schema, the description covers purpose, resource, and usage context. Could mention pagination behavior or clarify 'library' distinction from survey blocks, but 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 coverage is 100% with clear descriptions for both parameters. The description does not add extra parameter 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?

Clearly states the verb 'list', resource 'reusable survey blocks in a Qualtrics library', and the purpose of discovering complex block definitions. Distinguishes from sibling 'list_blocks' by specifying 'in a library'.

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?

Implies usage for discovery before copying/recreating but does not explicitly state when to use this tool versus alternatives like 'list_blocks'. No when-not or explicit alternative naming.

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