Apollo.io MCP Server

create_account

Create a company record in Apollo CRM by providing name and domain. Free to use.

Instructions

Create an account (company record) in your Apollo CRM. FREE. An account represents a company you're tracking. Provide at least the name and domain.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "create_account"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Company name
`domain`	No	Company domain, e.g. 'google.com'. Will be auto-cleaned.
`phone_number`	No	Company phone number
`raw_address`	No	Full company address
`owner_id`	No	Apollo user ID of the account owner

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 10, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Without annotations, the description must convey behavioral traits. It mentions 'FREE' and that the domain 'will be auto-cleaned', but does not disclose permissions, idempotency, or side effects of creating the record.

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?

Two concise, front-loaded sentences with no wasted words. Every sentence adds value: action, resource, cost, minimal requirements.

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 no output schema, the description sufficiently explains the tool's purpose and basic requirements. It could mention what the created account looks like or error cases, but overall adequate.

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 100%, so parameters are well-documented. The description adds marginal value: only 'will be auto-cleaned' for domain and a redundant example. Baseline 3 applies.

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 verb 'Create' and the resource 'account (company record) in your Apollo CRM', distinguishing it from update and other account-related tools. The mention of 'FREE' adds a unique selling point.

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?

It advises to 'provide at least the name and domain', but the schema only requires 'name'; 'domain' is optional. No explicit guidance on when to use this vs alternatives like 'update_account' or when not to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server