Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_survey_question_answers

Read-only

Retrieve answers submitted for a specific survey question. Paginate through results using count and offset.

Instructions

List answers for a single survey question.

Retrieves the individual answers submitted for one specific question within the specified survey. Use count and offset to page through large result sets.

Args: survey_id: The unique id of the survey. question_id: The unique id of the question whose answers to list. count: Number of records to return per page (default 10). offset: Number of records to skip for pagination (default 0).

Returns: JSON with the list of survey question answers.

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": {
      "survey_id": "<survey_id>",
      "question_id": "<question_id>"
    },
    "name": "get_survey_question_answers"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
offsetNo
accountNo
survey_idYes
question_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A4/5.0
Behavior3/5

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

Annotations (readOnlyHint: true, destructiveHint: false) already indicate a safe read operation. The description adds that it retrieves answers and returns JSON, but does not detail other behavioral aspects like rate limits or authorization. Value added beyond annotations is moderate.

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?

Description is very concise: one sentence for purpose followed by structured Args section. Every sentence adds value. No fluff or redundancy.

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?

With an output schema present, the description need not detail return format fully. It covers required params, pagination, and basic return structure. However, the undocumented 'account' parameter is a minor gap, preventing a perfect score.

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 documentation coverage is 0%, so description carries the burden. It explains survey_id, question_id, count, and offset with defaults and purpose. However, it omits the 'account' parameter (present in schema), leaving it undocumented. Thus, partial but not complete coverage.

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 'List answers for a single survey question' with specific verb 'list' and resource 'answers for a single survey question'. It distinguishes from sibling tools like get_survey_responses by emphasizing 'one specific question' and requiring both survey_id and question_id.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description provides clear usage context: retrieving answers for a specific question within a survey, with pagination guidance (count and offset). While it does not explicitly state when not to use it or name alternatives, the context of sibling tools makes differentiation clear.

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