Skip to main content
Glama
bcharleson

Instantly MCP Server

get_email

Retrieve a specific email by its unique ID to access and review email content or campaign details from the Instantly API.

Instructions

Get a specific email by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
email_idYesEmail ID/UUID

Implementation Reference

  • Main handler logic for 'get_email' tool: validates email_id parameter, calls Instantly API endpoint `/emails/{email_id}` to fetch email details, formats and returns the response.
    case 'get_email': {
      console.error('[Instantly MCP] 📧 Executing get_email...');
    
      if (!args.email_id) {
        throw new McpError(ErrorCode.InvalidParams, 'Email ID is required for get_email');
      }
    
      const emailResult = await makeInstantlyRequest(`/emails/${args.email_id}`, {}, apiKey);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({
              success: true,
              email: emailResult,
              message: 'Email retrieved successfully'
            }, null, 2)
          }
        ]
      };
    }
  • Zod schema for validating 'get_email' input parameters (requires email_id string).
    export const GetEmailSchema = z.object({
      email_id: z.string().min(1, { message: 'Email ID cannot be empty' })
    });
  • Tool registration/definition including name, description, annotations, and input schema for the MCP tools list.
    {
      name: 'get_email',
      title: 'Get Email',
      description: 'Get email details by ID',
      annotations: { readOnlyHint: true },
      inputSchema: {
        type: 'object',
        properties: {
          email_id: { type: 'string', description: 'Email UUID' }
        },
        required: ['email_id']
      }
    },
  • Central tools registry that includes emailTools (containing get_email) via aggregation from category files.
    export const TOOLS_DEFINITION = buildToolsDefinition();
  • Validation function for get_email parameters using the GetEmailSchema.
    export function validateGetEmailData(args: unknown): z.infer<typeof GetEmailSchema> {
      return validateWithSchema(GetEmailSchema, args, 'get_email');
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool fetches an email but lacks details on permissions required, rate limits, error handling (e.g., for invalid IDs), or response format. This is inadequate for a read operation that might have constraints, scoring low due to minimal behavioral insight.

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 extremely concise—a single, clear sentence that front-loads the core purpose without unnecessary words. Every part of the sentence ('Get a specific email by ID') contributes directly to understanding the tool, making it efficient 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 (1 parameter, no output schema, no annotations), the description is minimal but incomplete. It doesn't cover behavioral aspects like what data is returned or error conditions, which are crucial for effective use. For a basic read tool, more context on output or constraints would enhance completeness.

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 mentions 'by ID', which aligns with the single parameter 'email_id' in the schema. Since schema description coverage is 100%, the schema already documents this parameter fully. The description adds no additional semantic context (e.g., ID format or source), so it meets the baseline for high schema coverage without compensating value.

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 ('Get') and resource ('a specific email by ID'), making the purpose immediately understandable. It distinguishes this from sibling tools like 'list_emails' by specifying retrieval of a single item rather than listing. However, it doesn't explicitly mention what 'get' entails (e.g., fetching metadata, content, or both), which prevents a perfect score.

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. It doesn't mention when to choose 'get_email' over 'list_emails' for bulk retrieval or 'reply_to_email' for interaction, nor does it specify prerequisites like needing an email ID from another operation. Usage is implied but not explicitly stated.

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/bcharleson/Instantly-MCP'

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