Skip to main content
Glama
masridigital

Apollo.io MCP Server

by masridigital

create_account

Create a new organization account in Apollo.io by providing company details like name, domain, and contact information to establish a B2B sales presence.

Instructions

Create a new account/organization in Apollo with company details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCompany name
domainNoCompany domain
phone_numberNoCompany phone
website_urlNoWebsite URL

Implementation Reference

  • The handler function that implements the create_account tool. It sends a POST request to Apollo's /accounts endpoint with the provided arguments and returns a success message with the created account details.
    private async createAccount(args: any) {
      const response = await this.axiosInstance.post("/accounts", args);
      const account = response.data.account;
    
      return {
        content: [
          {
            type: "text",
            text: `Account created successfully!\nID: ${account.id}\nName: ${account.name}\nDomain: ${account.domain || "N/A"}`,
          },
        ],
      };
    }
  • Input schema for the create_account tool, defining the expected parameters: name (required), domain, phone_number, and website_url.
    inputSchema: {
      type: "object",
      properties: {
        name: {
          type: "string",
          description: "Company name",
        },
        domain: {
          type: "string",
          description: "Company domain",
        },
        phone_number: {
          type: "string",
          description: "Company phone",
        },
        website_url: {
          type: "string",
          description: "Website URL",
        },
      },
      required: ["name"],
    },
  • src/index.ts:516-542 (registration)
    Registration of the create_account tool in the getTools() array returned by ListToolsRequestSchema handler. Includes name, description, and input schema.
    {
      name: "create_account",
      description:
        "Create a new account/organization in Apollo with company details.",
      inputSchema: {
        type: "object",
        properties: {
          name: {
            type: "string",
            description: "Company name",
          },
          domain: {
            type: "string",
            description: "Company domain",
          },
          phone_number: {
            type: "string",
            description: "Company phone",
          },
          website_url: {
            type: "string",
            description: "Website URL",
          },
        },
        required: ["name"],
      },
    },
  • Dispatcher case in the CallToolRequestSchema handler that routes create_account calls to the createAccount method.
    case "create_account":
      return await this.createAccount(args);
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it creates an account with company details. It doesn't disclose behavioral traits like required permissions, whether the operation is idempotent, rate limits, or what happens on failure. This is inadequate for a mutation tool with zero annotation coverage.

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 a single, efficient sentence that front-loads the core purpose. Every word earns its place with no redundancy or unnecessary elaboration.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., account ID, success status) or address potential side effects, leaving significant gaps for agent understanding.

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 description coverage is 100%, so the schema fully documents all 4 parameters (name, domain, phone_number, website_url). The description adds no parameter-specific details beyond implying 'company details' map to these fields, meeting the baseline for high schema coverage.

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 ('Create') and resource ('new account/organization in Apollo'), specifying it's for company details. It distinguishes from siblings like 'create_contact' (for contacts) and 'enrich_organization' (for updating existing ones), but doesn't explicitly contrast with 'search_organizations' or 'get_account'.

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 on when to use this tool versus alternatives like 'enrich_organization' (for existing accounts) or 'search_organizations' (for finding accounts). The description implies usage for new accounts only, but lacks explicit exclusions or prerequisites.

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/masridigital/apollo.io-mcp'

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