Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_survey

Read-only

Retrieve full details of a Mailchimp survey, including questions, status, and public URL. Use the survey ID obtained from list_surveys.

Instructions

Retrieve full details for a single survey.

Use when you have a survey_id (from list_surveys) and need its questions, status, or public URL. Use publish_survey / unpublish_survey to change whether it is live.

Returns 404 error if list_id or survey_id is invalid.

Args: list_id: Audience/list ID (from list_audiences). survey_id: Survey ID (from list_surveys).

Returns: JSON survey object including id, title, status, url, questions, created_at, updated_at.

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": {
      "list_id": "<list_id>",
      "survey_id": "<survey_id>"
    },
    "name": "get_survey"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
list_idYes
survey_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true. Description adds value by specifying 404 error for invalid IDs and listing return fields (id, title, status, etc.), which are not covered by annotations. No contradiction.

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 132 words, front-loaded with purpose, then usage, error, and clearly labeled Args/Returns. No fluff; every sentence adds value.

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

Completeness5/5

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

Given the tool is simple (get a single survey) and output schema exists, the description provides sufficient details: purpose, usage, error behavior, parameter sources, and return preview. It is complete.

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

Parameters4/5

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

Schema has 0% description coverage, so description must compensate. It explains list_id as 'Audience/list ID (from list_audiences)' and survey_id as 'Survey ID (from list_surveys)', adding source context. The optional account parameter is not mentioned, but it is less critical.

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 'Retrieve full details for a single survey' with specific verb and resource. It differentiates from siblings like list_surveys and get_survey_report by focusing on full details including questions, status, and URL.

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?

Explicitly says to use when you have a survey_id from list_surveys and need questions/status/URL. Also directs to publish/unpublish for changing liveness. However, it does not explicitly mention when not to use or list all alternatives among siblings.

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