Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_survey_questions_report

Read-only

Retrieve aggregate survey responses broken down by each question to analyze how respondents answered.

Instructions

Get the questions report for a single survey.

Retrieves aggregate reporting broken down by each question in the specified survey. Use this to understand how respondents answered across all questions.

Args: survey_id: The unique id of the survey whose questions to report on.

Returns: JSON with the survey questions report.

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>"
    },
    "name": "get_survey_questions_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
survey_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already confirm readOnlyHint=true and destructiveHint=false. The description adds that it returns a JSON report, consistent with read-only behavior. No additional traits like pagination or authorization are disclosed, but annotations cover the safety profile.

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?

The description is concise with a clear front-loaded summary, followed by an elaboration, and structured args/returns. Every sentence adds value with no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, has an output schema, and annotations cover safety. However, the description fails to explain the 'account' parameter and does not detail the contents of the questions report (e.g., counts, percentages). It is adequate but has notable gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%; the description partially compensates by explaining survey_id ('The unique id of the survey whose questions to report on') but completely omits the optional 'account' parameter. Users would not know what 'account' is for.

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 'Get the questions report for a single survey' and explains it retrieves aggregate reporting per question. It distinguishes from siblings like get_survey_report (overall report) and get_survey_question_answers (individual answers).

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?

The description says 'Use this to understand how respondents answered across all questions,' providing clear context. However, it does not explicitly mention when not to use it or name specific alternatives like get_survey_report.

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