Skip to main content
Glama
MrNewDelhi

Mailosaur MCP

by MrNewDelhi

mailosaur_analysis_deliverability

Run deliverability analysis on an email message using its ID to assess inbox placement and identify delivery issues.

Instructions

Run deliverability analysis for a message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageIdYes

Implementation Reference

  • src/index.ts:398-408 (registration)
    Registration of the 'mailosaur_analysis_deliverability' tool via server.tool(), including its schema (z.object({ messageId: z.string() })) and handler.
    server.tool(
      "mailosaur_analysis_deliverability",
      "Run deliverability analysis for a message.",
      {
        messageId: z.string()
      },
      async ({ messageId }) => {
        const result = await mailosaur.analysis.deliverability(messageId);
        return response(result);
      }
    );
  • Input schema for the tool: expects a single 'messageId' string parameter.
    {
      messageId: z.string()
    },
  • Handler function that calls mailosaur.analysis.deliverability(messageId) and returns the result.
    async ({ messageId }) => {
      const result = await mailosaur.analysis.deliverability(messageId);
      return response(result);
  • The 'response' helper function that wraps the result in MCP content format (JSON.stringify).
    function response(value: unknown) {
      return {
        content: [
          {
            type: "text" as const,
            text: JSON.stringify(value, null, 2)
          }
        ]
      };
    }
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as read-only or destructive nature, authentication requirements, or side effects. The description is completely lacking in this dimension.

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

Conciseness2/5

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

The description is very short (one sentence), but it is under-specified rather than concise. It fails to provide necessary information in an efficient manner.

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 presence of sibling analysis tools and no output schema, the description is incomplete. It does not explain what deliverability analysis entails, what the return value contains, or how it differs from spam analysis.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, and the tool description does not add any meaning to the single parameter 'messageId'. The agent receives no guidance on what this parameter represents or how to format it.

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 action ('Run deliverability analysis') and the resource ('a message'). It distinguishes from the sibling tool 'mailosaur_analysis_spam' by specifying 'deliverability', making the purpose clear.

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 (e.g., mailosaur_analysis_spam). There is no mention of prerequisites, context, or exclusions.

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/MrNewDelhi/mailosaur-mcp'

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