Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_file_folders

Read-only

Retrieve file folders in your Mailchimp File Manager to obtain folder_id values for organizing uploads.

Instructions

List folders in the account's File Manager.

Use to discover folder_id values for organizing or targeting uploads via upload_file. Use list_files to see the files themselves.

Args: count: Folders to return (1-1000, default 10). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and folders array. Each folder: id (use as folder_id), name, file_count, created_at, created_by.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_file_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
offsetNo
accountNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate read-only. The description adds valuable details on return structure (total_items, folders array) and pagination behavior (offset usage). No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise with a brief purpose, usage guidelines, and clear Args/Returns sections. No extraneous text, though slightly verbose for a simple list operation.

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?

Covers purpose, usage, and most parameters, but missing explanation for the optional account parameter. Output schema present, reducing need for return details. Not fully complete.

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?

With 0% schema coverage, the description defines count and offset (range and purpose) but omits the account parameter. Adds meaning for 2 of 3 parameters, partially compensating for schema 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 the tool lists folders in the account's File Manager, a specific verb+resource. It distinguishes from siblings like list_files and upload_file by explicitly mentioning their use cases.

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 states when to use: to discover folder_id for uploads via upload_file. Also directs to list_files for seeing files themselves, providing clear alternative 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