Skip to main content
Glama
AgentX-ai

Mailchimp MCP Server

by AgentX-ai

get_file

Retrieve specific file details from your Mailchimp account using the file ID to access email marketing assets and content.

Instructions

Get details of a specific file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_idYesThe file ID

Implementation Reference

  • Handler for the 'get_file' tool: retrieves the file using MailchimpService and returns a JSON-formatted text response.
    case "get_file":
      const file = await service.getFile(args.file_id);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(file, null, 2),
          },
        ],
      };
  • Tool registration definition for 'get_file', including name, description, and input schema.
    {
      name: "get_file",
      description: "Get details of a specific file",
      inputSchema: {
        type: "object",
        properties: {
          file_id: {
            type: "string",
            description: "The file ID",
          },
        },
        required: ["file_id"],
      },
    },
  • TypeScript interface defining the structure of the MailchimpFile response object used as output schema for the get_file tool.
    export interface MailchimpFile {
      id: string;
      folder_id: string;
      name: string;
      file_data: string;
      type: string;
      size: number;
      created_at: string;
      created_by: string;
      _links?: Array<{
        rel: string;
        href: string;
        method: string;
        targetSchema?: string;
        schema?: string;
      }>;
    }
  • Service helper method that performs the actual API call to retrieve file details from Mailchimp's File Manager.
    async getFile(fileId: string): Promise<MailchimpFile> {
      return await this.makeRequest(`/file-manager/files/${fileId}`);
    }
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' which implies a read-only operation, but doesn't specify permissions required, error handling, rate limits, or what 'details' include (e.g., metadata, content). For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior and constraints.

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, directly stating the tool's purpose. It's front-loaded and appropriately sized for a simple retrieval tool, making it easy for an agent to parse quickly without unnecessary elaboration.

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 the tool's simplicity (1 parameter, no output schema, no annotations), the description is minimal but incomplete. It doesn't explain what 'details' are returned, potential errors, or how it fits within the broader context of sibling tools. For a tool with no output schema or annotations, more contextual information would help the agent use it effectively.

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?

The input schema has 100% description coverage, with 'file_id' clearly documented as 'The file ID'. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or sourcing instructions. With high schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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

Purpose3/5

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

The description 'Get details of a specific file' clearly states the action (get) and resource (file), but it's vague about what 'details' entail and doesn't differentiate from sibling tools like 'list_files' or 'get_folder'. It's functional but lacks specificity to distinguish it from similar retrieval operations.

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_files' for multiple files or other 'get_' tools for different resources. The description implies usage for a single file but doesn't specify prerequisites, exclusions, or contextual alternatives, leaving the agent to infer based on naming conventions alone.

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