Skip to main content
Glama
getplatform

GetMailer MCP Server

by getplatform

get_analytics

Retrieve email analytics and statistics from GetMailer MCP Server to monitor campaign performance and track engagement metrics.

Instructions

Get email analytics and statistics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoType of analytics (summary or daily)
daysNoNumber of days for daily stats (default: 30)

Implementation Reference

  • Handler for the 'get_analytics' tool that constructs an API request to fetch analytics data based on the provided type ('summary' or 'daily') and days parameters, then returns the JSON response as formatted text content.
    case 'get_analytics': {
      const type = args?.type || 'summary';
      const days = args?.days || 30;
      const result = await apiRequest(`/api/analytics?type=${type}&days=${days}`);
      return {
        content: [{ type: 'text' as const, text: JSON.stringify(result, null, 2) }],
      };
    }
  • src/index.ts:220-237 (registration)
    Registration of the 'get_analytics' tool in the listTools response, including its name, description, and input schema defining optional 'type' (enum: summary, daily) and 'days' (number) parameters.
    {
      name: 'get_analytics',
      description: 'Get email analytics and statistics',
      inputSchema: {
        type: 'object' as const,
        properties: {
          type: {
            type: 'string',
            enum: ['summary', 'daily'],
            description: 'Type of analytics (summary or daily)',
          },
          days: {
            type: 'number',
            description: 'Number of days for daily stats (default: 30)',
          },
        },
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does, not how it behaves. It doesn't disclose whether this is a read-only operation, what permissions are needed, if there are rate limits, or what format the analytics return. 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 zero wasted words. It's appropriately sized and front-loaded with the core purpose.

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?

For a tool with no annotations and no output schema, the description is insufficient. It doesn't explain what analytics are returned, their format, or any behavioral constraints. The agent would be guessing about the tool's behavior and output.

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 description adds no parameter information beyond what's already in the schema (which has 100% coverage). It doesn't explain what 'summary' vs 'daily' analytics include, or how the 'days' parameter affects results. Baseline 3 is appropriate since the schema does the heavy lifting.

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 clearly states the verb 'Get' and the resource 'email analytics and statistics', making the purpose immediately understandable. However, it doesn't differentiate this tool from potential sibling analytics tools (none exist in the sibling list), so it's not a perfect 5.

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. There's no mention of prerequisites, context, or comparison with other tools like 'get_email' or 'list_emails' that might provide related data.

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/getplatform/getmailer-mcp'

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