Skip to main content
Glama
bcharleson

Instantly MCP Server

create_account

Create email accounts with IMAP/SMTP credentials for Google Workspace, Microsoft 365, AWS SES, or generic IMAP providers to enable email sending functionality.

Instructions

Create email account with IMAP/SMTP credentials.

Provider codes:

  • 1: IMAP (generic)

  • 2: Google Workspace

  • 3: Microsoft 365

  • 4: AWS SES

Requires valid IMAP and SMTP credentials for email sending.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the create_account tool. It constructs the request body from input parameters and sends a POST request to the /accounts endpoint using the API client.
    async def create_account(params: CreateAccountInput) -> str:
        """
        Create email account with IMAP/SMTP credentials.
        
        Provider codes:
        - 1: IMAP (generic)
        - 2: Google Workspace
        - 3: Microsoft 365
        - 4: AWS SES
        
        Requires valid IMAP and SMTP credentials for email sending.
        """
        client = get_client()
        
        body = {
            "email": params.email,
            "first_name": params.first_name,
            "last_name": params.last_name,
            "provider_code": params.provider_code,
            "imap_username": params.imap_username,
            "imap_password": params.imap_password,
            "imap_host": params.imap_host,
            "imap_port": params.imap_port,
            "smtp_username": params.smtp_username,
            "smtp_password": params.smtp_password,
            "smtp_host": params.smtp_host,
            "smtp_port": params.smtp_port,
        }
        
        result = await client.post("/accounts", json=body)
        return json.dumps(result, indent=2)
  • Pydantic model defining the input schema for the create_account tool, including all required fields like email, names, provider_code, IMAP/SMTP credentials.
    class CreateAccountInput(BaseModel):
        """Input for creating an email account with IMAP/SMTP credentials."""
        
        model_config = ConfigDict(str_strip_whitespace=True, extra="ignore")
        
        email: str = Field(..., description="Email address")
        first_name: str = Field(..., description="First name")
        last_name: str = Field(..., description="Last name")
        provider_code: Literal[1, 2, 3, 4] = Field(
            ..., description="1=IMAP, 2=Google, 3=Microsoft, 4=AWS"
        )
        imap_username: str = Field(..., description="IMAP username")
        imap_password: str = Field(..., description="IMAP password")
        imap_host: str = Field(..., description="IMAP host (e.g., imap.gmail.com)")
        imap_port: int = Field(..., description="IMAP port (e.g., 993)")
        smtp_username: str = Field(..., description="SMTP username")
        smtp_password: str = Field(..., description="SMTP password")
        smtp_host: str = Field(..., description="SMTP host (e.g., smtp.gmail.com)")
        smtp_port: int = Field(..., description="SMTP port (e.g., 587)")
  • The create_account function is included in the ACCOUNT_TOOLS list, which collects account tools for registration with the MCP server.
    ACCOUNT_TOOLS = [
        list_accounts,
        get_account,
        create_account,
        update_account,
        manage_account_state,
        delete_account,
    ]
  • TOOL_ANNOTATIONS entry for create_account specifying destructiveHint: False, applied during tool registration in register_tools() function.
    # Account tools
    "list_accounts": {"readOnlyHint": True},
    "get_account": {"readOnlyHint": True},
    "create_account": {"destructiveHint": False},
    "update_account": {"destructiveHint": False},
    "manage_account_state": {"destructiveHint": False},
    "delete_account": {"destructiveHint": True, "confirmationRequiredHint": True},
Behavior3/5

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

Annotations provide 'destructiveHint: false', indicating it's not destructive. The description adds context about required credentials and provider codes, which helps understand behavioral needs beyond annotations. However, it doesn't mention rate limits, authentication requirements beyond credentials, or what happens on success/failure, leaving some behavioral aspects unclear.

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

Conciseness4/5

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

The description is appropriately sized with two clear sections: purpose statement and provider codes, followed by credential requirements. It's front-loaded with the main action. Minor improvement could be integrating the credential note more seamlessly, but overall it's efficient with zero wasted sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (12 parameters, creation operation) and the presence of an output schema (which handles return values), the description provides good context: purpose, provider mapping, and credential requirements. It covers key aspects needed for invocation, though additional details on error cases or side effects would enhance completeness.

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

Parameters4/5

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

Schema description coverage is 0%, so the description carries full burden. It explains provider codes (1-4 mapping to services) and emphasizes credential requirements, adding meaningful context beyond the bare parameter names in the schema. However, it doesn't detail all 12 parameters individually, leaving some semantics implicit.

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

Purpose5/5

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

The description clearly states the specific action ('Create email account') and the resources involved ('with IMAP/SMTP credentials'), distinguishing it from sibling tools like 'update_account' or 'delete_account'. It precisely communicates what the tool does beyond just restating the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by mentioning 'Requires valid IMAP and SMTP credentials for email sending', which suggests prerequisites. However, it doesn't explicitly state when to use this tool versus alternatives like 'update_account' or 'manage_account_state', nor does it provide exclusion criteria or direct comparisons to sibling tools.

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-python'

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