Skip to main content
Glama
AgentX-ai

Mailchimp MCP Server

by AgentX-ai

get_store

Retrieve specific store details from Mailchimp's Marketing API to access comprehensive e-commerce data for marketing analysis and campaign management.

Instructions

Get details of a specific store

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
store_idYesThe store ID

Implementation Reference

  • Handler case in handleToolCall function that executes the get_store tool by calling the service method and returning formatted JSON response.
    case "get_store":
      const store = await service.getStore(args.store_id);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(store, null, 2),
          },
        ],
      };
  • Input schema defining the required 'store_id' parameter for the get_store tool.
    inputSchema: {
      type: "object",
      properties: {
        store_id: {
          type: "string",
          description: "The store ID",
        },
      },
      required: ["store_id"],
  • Registration of the get_store tool in the getToolDefinitions array, including name, description, and schema.
    {
      name: "get_store",
      description: "Get details of a specific store",
      inputSchema: {
        type: "object",
        properties: {
          store_id: {
            type: "string",
            description: "The store ID",
          },
        },
        required: ["store_id"],
      },
    },
  • Helper method in MailchimpService that performs the actual API request to fetch store details from Mailchimp's e-commerce endpoint.
    async getStore(storeId: string): Promise<MailchimpStore> {
      return await this.makeRequest(`/ecommerce/stores/${storeId}`);
    }
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 the action ('Get details') but does not disclose any behavioral traits such as read-only nature, error handling, authentication needs, rate limits, or what 'details' includes. 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 ('Get details of a specific store') that is front-loaded and wastes no words. It directly conveys the core purpose without unnecessary elaboration, making it highly concise and well-structured.

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 (one parameter, no output schema, no annotations), the description is minimal. It lacks context on what 'details' entail, how to handle errors, or any behavioral aspects, making it incomplete for effective agent use despite the straightforward schema.

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 'store_id' documented as 'The store ID'. The description does not add any meaning beyond this, such as format examples or constraints. Since schema coverage is high, the baseline score of 3 is appropriate, as the description does not compensate but also does not detract.

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 store' clearly states the verb ('Get') and resource ('store'), making the purpose understandable. However, it does not differentiate this tool from sibling tools like 'list_stores' or other 'get_' tools, which would require specifying what 'details' entails or the scope of retrieval.

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?

The description provides no guidance on when to use this tool versus alternatives. For example, it does not mention that 'list_stores' should be used to retrieve multiple stores or that 'get_store' is for a single store by ID, leaving the agent to infer usage from context without explicit direction.

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