Skip to main content
Glama
jgottlieb84

agentline-mcp

by jgottlieb84

release_email_address

Release a previously provisioned email address by providing its unique address ID to free up resources.

Instructions

Release a provisioned email address. Pass the id returned from create_email_address (NOT the full email string).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
address_idYes

Implementation Reference

  • The MCP tool handler for `release_email_address`. Decorated with @mcp.tool(), it accepts an `address_id` string, calls the underlying SDK client's `release_email_address` method, and returns a dict with `address_id` and `released` status. Errors are caught and returned as error dicts.
    @mcp.tool()
    def release_email_address(address_id: str) -> dict:
        """Release a provisioned email address. Pass the `id` returned from
        `create_email_address` (NOT the full email string).
        """
        try:
            released = _client_or_init().release_email_address(address_id)
            return {"address_id": address_id, "released": released}
        except AgentlineError as e:
            return {"error": str(e), "status_code": e.status_code}
  • The tool is registered as an MCP tool via the `@mcp.tool()` decorator on the `release_email_address` function.
    @mcp.tool()
  • `release_email_address` is also called inside the `capture_email_code` function's `finally` block, to release the email address after capturing a verification code (when `release_after=True`).
    if release_after:
        client.release_email_address(addr.id)
Behavior2/5

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

No annotations are provided, so the description must carry full burden. It states 'release' implying mutation but does not disclose behavioral traits like reversibility, side effects, or required permissions, which is insufficient for a mutation tool.

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 two sentences, front-loaded with the purpose, and contains no extraneous information. Every sentence earns its place.

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?

For a simple tool with one parameter and no output schema, the description covers the essential purpose and parameter usage. It lacks behavioral details, but given the complexity, it is reasonably complete.

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?

Schema coverage is 0% but the description adds value by clarifying the parameter's origin (id from create_email_address) and distinguishing it from the email string. However, it does not specify format or constraints beyond the schema's type string.

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 action 'Release a provisioned email address' with a specific verb and resource, distinguishing it from sibling tools like create_email_address or list_email_addresses.

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

Usage Guidelines4/5

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

The description explicitly instructs to pass the id from create_email_address and not the full email string, providing clear guidance on parameter source and preventing misuse. However, it does not specify when not to use or name alternatives.

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