Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

unpublish_survey

Unpublish a currently live survey, taking it offline. Requires audience list ID and survey ID.

Instructions

Unpublish a survey that is currently live, taking it offline.

Use list_surveys to find the survey_id and confirm it is published. Use publish_survey to put it back live.

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

Returns: JSON with status 'unpublished' and the survey_id, or an error object.

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": "unpublish_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.4/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, matching the description's write operation. Returns status 'unpublished' or error. Does not mention idempotency consequences, but annotations already hint at non-idempotent.

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?

Concise with clear Args/Returns sections. First sentence states purpose directly. No redundant information.

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?

Describes return value well. But missing explanation of the 'account' parameter limits completeness. Has output schema documented, reducing need to detail return structure.

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?

Covers two required params (list_id, survey_id) with origin notes, but omits the optional 'account' parameter. Schema coverage is 0%, so description should explain all params; missing one is a gap.

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 it unpublishes a live survey, taking it offline. It distinguishes from publish_survey and list_surveys by referencing them as prerequisites/alternatives.

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

Usage Guidelines5/5

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

Explicitly says to use list_surveys to find survey_id and confirm published state, and that publish_survey can restore it. Provides clear when-to-use guidance.

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