Skip to main content
Glama
jgottlieb84

agentline-mcp

by jgottlieb84

send_email

Send outbound emails from a provisioned address to any recipient. Specify subject, body, and optional reply-to or HTML content for communication via the agentline platform.

Instructions

Send an outbound email from a provisioned address. from_email must be one of your provisioned addresses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_emailYes
to_emailYes
subjectYes
bodyYes
body_htmlNo
reply_toNo

Implementation Reference

  • The send_email tool handler function. It is decorated with @mcp.tool(), accepts from_email, to_email, subject, body, optional body_html and reply_to parameters, and delegates to the Agentline SDK client's send_email method.
    @mcp.tool()
    def send_email(
        from_email: str,
        to_email: str,
        subject: str,
        body: str,
        body_html: str | None = None,
        reply_to: str | None = None,
    ) -> dict:
        """Send an outbound email from a provisioned address. `from_email` must be
        one of your provisioned addresses.
        """
        try:
            return _client_or_init().send_email(
                from_=from_email,
                to=to_email,
                subject=subject,
                body=body,
                body_html=body_html,
                reply_to=reply_to,
            )
        except AgentlineError as e:
            return {"error": str(e), "status_code": e.status_code}
  • The @mcp.tool() decorator registers send_email as an MCP tool on the FastMCP server instance.
    @mcp.tool()
  • The type annotations on the send_email function parameters serve as the input schema, defining that from_email, to_email, subject, and body are required strings, while body_html and reply_to are optional strings.
    def send_email(
        from_email: str,
        to_email: str,
        subject: str,
        body: str,
        body_html: str | None = None,
        reply_to: str | None = None,
    ) -> dict:
Behavior2/5

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

The description is brief and does not disclose behavioral traits beyond the sending action and the provisioned requirement. It lacks information on side effects, success/failure behavior, rate limits, or whether the email is sent immediately. Since no annotations are provided, the description carries full burden but fails to address these.

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, using two sentences that directly state the purpose and a key constraint. Every word contributes, with no filler or repetition.

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 has 6 parameters, no output schema, and no annotations, the description is insufficiently complete. It does not mention prerequisites beyond provisioned address, does not explain return values, and does not cover optional parameters like body_html and reply_to. The agent would lack important context for correct invocation.

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

Parameters2/5

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

With 0% schema description coverage, the description only adds meaning to the from_email parameter by stating it must be provisioned. The other five parameters (to_email, subject, body, body_html, reply_to) receive no explanation beyond their names and types in the schema. This leaves the agent without guidance on formatting or constraints.

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 it sends an outbound email from a provisioned address, using specific verb and resource. It distinguishes from sibling tools like send_sms and wait_for_email by specifying email and outbound. No ambiguity.

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 only notes that from_email must be provisioned, but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention any exclusions. Among siblings, there is no other email sender, so usage is implied but not explicitly recommended.

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/jgottlieb84/agentline-mcp'

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