Skip to main content
Glama
FromSmall2Big

Apollo.io MCP Server

create_account

Create a new Apollo.io account by providing name, domain, phone number, and address information for sales and marketing lead generation.

Instructions

Create a new account in Apollo.io.

This tool creates a new account with the provided information. The domain and address will be intelligently parsed for additional data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
domainNo
phone_numberNo
raw_addressNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'create_account' tool. Decorated with @mcp.tool() for automatic registration in FastMCP. Posts account creation data to Apollo.io API.
    @mcp.tool()
    async def create_account(
        name: str,
        domain: Optional[str] = None,
        phone_number: Optional[str] = None,
        raw_address: Optional[str] = None
    ) -> Dict[str, Any]:
        """
        Create a new account in Apollo.io.
        
        This tool creates a new account with the provided information.
        The domain and address will be intelligently parsed for additional data.
        """
        endpoint = "/v1/accounts"
        
        data = {"name": name}
        if domain:
            data["domain"] = domain
        if phone_number:
            data["phone_number"] = phone_number
        if raw_address:
            data["raw_address"] = raw_address
        
        try:
            result = await apollo_client.make_request("POST", endpoint, data=data)
            return result
        except httpx.HTTPStatusError as e:
            return {"error": f"API request failed: {e.response.status_code} {e.response.text}"}
        except Exception as e:
            return {"error": f"Request failed: {str(e)}"}
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions that domain and address will be 'intelligently parsed for additional data', it doesn't disclose important behavioral traits like authentication requirements, rate limits, whether this is a write operation (implied but not stated), what happens on duplicate accounts, or what the response contains. The description adds minimal behavioral context beyond the basic operation.

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 concise with two sentences. The first sentence clearly states the core purpose, and the second adds useful information about intelligent parsing. There's no wasted verbiage, though the second sentence could be more specific about what 'additional data' means.

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

Completeness3/5

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

Given that there's an output schema (which handles return values), no annotations, and 4 parameters with 0% schema coverage, the description is incomplete. It provides basic purpose but lacks crucial context about parameter usage, behavioral constraints, and differentiation from sibling tools. For a creation tool with multiple parameters, this leaves significant gaps in understanding.

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 and 4 parameters (only 1 required), the description provides almost no parameter guidance. It mentions that 'domain and address will be intelligently parsed' which hints at how those parameters might be used, but doesn't explain the purpose of 'name' (the only required parameter) or 'phone_number', nor does it provide format expectations, constraints, or examples for any parameters.

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

Purpose3/5

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

The description states 'Create a new account in Apollo.io' which provides a clear verb ('Create') and resource ('account'), but it doesn't differentiate from sibling tools like 'update_account' or 'get_account_by_id'. The second sentence is somewhat tautological, restating the tool name rather than adding specificity about what makes this creation tool unique.

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 about when to use this tool versus alternatives like 'update_account' or 'get_account_by_id'. The description mentions intelligent parsing of domain and address, but doesn't explain when this tool is preferred over other account-related operations or what prerequisites might exist.

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/FromSmall2Big/Apollo-MCP'

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