Skip to main content
Glama
AgentX-ai

Mailchimp MCP Server

by AgentX-ai

get_folder

Retrieve details for a specific Mailchimp folder by providing its folder ID to access email marketing data.

Instructions

Get details of a specific folder

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_idYesThe folder ID

Implementation Reference

  • The handler logic within handleToolCall for the "get_folder" tool. It calls the MailchimpService.getFolder method with the provided folder_id and returns the folder details as a JSON-formatted text response.
    case "get_folder":
      const folder = await service.getFolder(args.folder_id);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(folder, null, 2),
          },
        ],
      };
  • Registration of the "get_folder" tool in the getToolDefinitions function, including name, description, and input schema.
    {
      name: "get_folder",
      description: "Get details of a specific folder",
      inputSchema: {
        type: "object",
        properties: {
          folder_id: {
            type: "string",
            description: "The folder ID",
          },
        },
        required: ["folder_id"],
      },
    },
  • Input schema definition for the "get_folder" tool, specifying folder_id as a required string parameter.
    inputSchema: {
      type: "object",
      properties: {
        folder_id: {
          type: "string",
          description: "The folder ID",
        },
      },
      required: ["folder_id"],
    },
  • The MailchimpService helper method that performs the actual API call to retrieve folder details using the Mailchimp API endpoint /campaign-folders/{folderId}.
    async getFolder(folderId: string): Promise<MailchimpFolder> {
      return await this.makeRequest(`/campaign-folders/${folderId}`);
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get details' but does not specify what details are returned, whether it's a read-only operation, error handling (e.g., for invalid IDs), or performance aspects. This is inadequate for a tool with no annotation coverage.

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 a single, efficient sentence with no wasted words, making it easy to parse and front-loaded with the core action. It appropriately sized for a simple tool.

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

Completeness2/5

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

Given no annotations, no output schema, and a simple input schema, the description is incomplete. It lacks details on return values, error cases, or behavioral traits, which are crucial for an agent to use the tool effectively in context with siblings like 'list_folders'.

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 description coverage is 100%, with the parameter 'folder_id' documented in the schema. The description adds no additional meaning beyond the schema, such as format examples or constraints, but the high schema coverage justifies a baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get details of a specific folder' clearly states the verb ('Get') and resource ('folder'), making the purpose understandable. However, it does not differentiate from sibling tools like 'get_file' or 'list_folders', which would require specifying what 'details' entail (e.g., metadata, contents, or permissions).

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as 'list_folders' or other 'get_' tools. The description implies usage for a specific folder but lacks context on prerequisites, error conditions, or comparisons to siblings, leaving the agent to infer usage scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AgentX-ai/mailchimp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server