Skip to main content
Glama
masridigital

Apollo.io MCP Server

by masridigital

create_contact

Add new contacts to Apollo.io with essential details including name, email, job title, company information, LinkedIn URL, and phone numbers to build and maintain your B2B sales database.

Instructions

Create a new contact in Apollo with details like name, email, title, company, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
first_nameYesFirst name
last_nameYesLast name
emailNoEmail address
titleNoJob title
organization_nameNoCompany name
linkedin_urlNoLinkedIn URL
phone_numbersNoPhone numbers

Implementation Reference

  • The main handler function that executes the create_contact tool logic by posting contact data to Apollo's /contacts API endpoint and returning a success message with the created contact's details.
    private async createContact(args: any) {
      const response = await this.axiosInstance.post("/contacts", args);
      const contact = response.data.contact;
    
      return {
        content: [
          {
            type: "text",
            text: `Contact created successfully!\nID: ${contact.id}\nName: ${contact.first_name} ${contact.last_name}\nEmail: ${contact.email || "N/A"}`,
          },
        ],
      };
    }
  • Input schema defining the parameters for the create_contact tool, including required first_name and last_name, and optional fields like email, title, organization_name, linkedin_url, and phone_numbers.
    inputSchema: {
      type: "object",
      properties: {
        first_name: {
          type: "string",
          description: "First name",
        },
        last_name: {
          type: "string",
          description: "Last name",
        },
        email: {
          type: "string",
          description: "Email address",
        },
        title: {
          type: "string",
          description: "Job title",
        },
        organization_name: {
          type: "string",
          description: "Company name",
        },
        linkedin_url: {
          type: "string",
          description: "LinkedIn URL",
        },
        phone_numbers: {
          type: "array",
          items: { type: "string" },
          description: "Phone numbers",
        },
      },
      required: ["first_name", "last_name"],
    },
  • src/index.ts:442-481 (registration)
    Registration of the create_contact tool in the getTools() method, specifying name, description, and input schema for MCP server.
    {
      name: "create_contact",
      description:
        "Create a new contact in Apollo with details like name, email, title, company, etc.",
      inputSchema: {
        type: "object",
        properties: {
          first_name: {
            type: "string",
            description: "First name",
          },
          last_name: {
            type: "string",
            description: "Last name",
          },
          email: {
            type: "string",
            description: "Email address",
          },
          title: {
            type: "string",
            description: "Job title",
          },
          organization_name: {
            type: "string",
            description: "Company name",
          },
          linkedin_url: {
            type: "string",
            description: "LinkedIn URL",
          },
          phone_numbers: {
            type: "array",
            items: { type: "string" },
            description: "Phone numbers",
          },
        },
        required: ["first_name", "last_name"],
      },
    },
  • Dispatcher case in the main tool handling switch statement that routes create_contact requests to the specific createContact handler method.
    case "create_contact":
      return await this.createContact(args);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates a contact but doesn't mention permissions required, whether the operation is idempotent, error handling, or what the response looks like (e.g., success/failure indicators). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence that front-loads the purpose ('Create a new contact in Apollo') and includes relevant examples. There's no wasted text, though it could be slightly more structured by explicitly mentioning key parameters or outcomes.

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 complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., side effects, error cases), usage context, and what to expect upon success or failure, making it inadequate for safe and effective tool invocation by an AI agent.

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 7 parameters. The description adds minimal value by listing examples like 'name, email, title, company, etc.', which loosely maps to parameters but doesn't provide additional syntax, constraints, or meaning beyond what's in the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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 a new contact') and resource ('in Apollo'), with examples of details like name, email, title, company. It distinguishes from siblings like 'update_contact' by specifying creation rather than modification, though it doesn't explicitly contrast with all alternatives like 'enrich_person'.

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_person' or 'update_contact' is provided. The description implies usage for creating new contacts but lacks explicit context, prerequisites, or exclusions, leaving the agent to infer based on the verb 'Create' alone.

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