Skip to main content
Glama

AIsa Sales

by one.aisa
OverviewDiscussionsAdmin

Create a Contact

post_apollo_contacts
Destructive

Create a new contact. Requires a master API key.

Published reference price: $0.012 USD per successful request. Account-specific pricing and final settlement may differ.

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / account_id
      Removed value: -{
-  "description": "Account ID",
-  "type": "string"
-}
    • addedInput schema / properties / body
      Added value: +{
+  "properties": {
+    "account_id": {
+      "description": "The Apollo ID for the account. Example: `63f53afe4ceeca00016bdd2f`",
+      "type": "string"
+    },
+    "contact_stage_id": {
+      "description": "The Apollo ID for the contact stage. Example: `6095a710bd01d100a506d4ae`",
+      "type": "string"
+    },
+    "corporate_phone": {
+      "description": "The work/office phone number. Example: `+44 7700 900852`",
+      "type": "string"
+    },
+    "direct_phone": {
+      "description": "The primary phone number. Example: `555-555-0133`",
+      "type": "string"
+    },
+    "email": {
+      "description": "The email address of the contact. Example: `example@email.com`",
+      "type": "string"
+    },
+    "first_name": {
+      "description": "The first name of the contact you want to create. Example: `Tim`",
+      "type": "string"
+    },
+    "home_phone": {
+      "description": "The home phone number. Example: `555-555-0133`",
+      "type": "string"
+    },
+    "label_names": {
+      "description": "Lists to which the contact belongs.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "last_name": {
+      "description": "The last name of the contact you want to create. Example: `Zheng`",
+      "type": "string"
+    },
+    "mobile_phone": {
+      "description": "The mobile phone number. Example: `555-555-0133`",
+      "type": "string"
+    },
+    "organization_name": {
+      "description": "The name of the contact's employer (company). Example: `apollo`",
+      "type": "string"
+    },
+    "other_phone": {
+      "description": "Alternative phone number. Example: `555-555-0133`",
+      "type": "string"
+    },
+    "present_raw_address": {
+      "description": "The personal location for the contact. Example: `Atlanta, United States`",
+      "type": "string"
+    },
+    "run_dedupe": {
+      "default": false,
+      "description": "Set to `true` to match against your existing contacts instead of always creating a new one. The default value is `false`. <br><br>When a match is found, Apollo **updates that existing contact in place** with the values you sent and returns it — the `id` in the response belongs to the pre-existing contact, not a new record. Fields you send overwrite the stored values, fields you omit are left untouched, and sending an empty value clears the field. <br><br>Matching is checked in order: `id`, CRM identifiers, `person_id`, `email` (against the contact's primary and additional emails), then name plus company. Because of the last rule, a contact can be matched and updated even when the email differs. <br><br>When deduplication is enabled, performance may be slightly impacted due to the additional matching checks. See the endpoint description for full details.",
+      "type": "boolean"
+    },
+    "title": {
+      "description": "The current job title that the contact holds. Example: `senior research analyst`",
+      "type": "string"
+    },
+    "typed_custom_fields": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "description": "Add information to <a href=\"https://knowledge.apollo.io/hc/en-us/articles/4412498825869-Create-Custom-Contact-Fields\" target=\"_blank\">custom fields</a> in Apollo. <br><br><b>Your custom fields are unique to your team's Apollo account. This means that the examples in this documentation may not work for your testing purposes.</b> <br><br>To utilize this parameter successfully, call the <a href=\"https://docs.apollo.io/reference/get-a-list-of-all-custom-fields\">get a list of all custom fields</a> endpoint and identify the `id` value for the custom field, as well as the appropriate data type. For example, if a custom field accepts picklist entries, you need to pass the accompanying `id` value for the picklist entry that you want to use as the input value. <br><br><b>Example</b>: When the <a href=\"https://docs.apollo.io/reference/get-a-list-of-all-custom-fields\">get a list of all custom fields</a> endpoint returns an `id` of field: \n * `\"60c39ed82bd02f01154c470a\"` (datetime) \n \n\n then the value passed should be: \n\n `{\"60c39ed82bd02f01154c470a\": \"2025-08-07\"}`",
+      "example": {
+        "60c39ed82bd02f01154c470a": "2025-08-07"
+      },
+      "type": "object"
+    },
+    "website_url": {
+      "description": "The corporate website URL. Example: `https://www.apollo.io/`",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • removedInput schema / properties / contact_stage_id
      Removed value: -{
-  "description": "Contact stage ID",
-  "type": "string"
-}
    • removedInput schema / properties / corporate_phone
      Removed value: -{
-  "description": "Corporate phone",
-  "type": "string"
-}
    • removedInput schema / properties / direct_phone
      Removed value: -{
-  "description": "Direct phone",
-  "type": "string"
-}
    • removedInput schema / properties / email
      Removed value: -{
-  "description": "Email",
-  "type": "string"
-}
    • removedInput schema / properties / first_name
      Removed value: -{
-  "description": "First name",
-  "type": "string"
-}
    • removedInput schema / properties / home_phone
      Removed value: -{
-  "description": "Home phone",
-  "type": "string"
-}
    • removedInput schema / properties / label_names
      Removed value: -{
-  "description": "Labels to set on the contact",
-  "type": "string"
-}
    • removedInput schema / properties / last_name
      Removed value: -{
-  "description": "Last name",
-  "type": "string"
-}
    • removedInput schema / properties / mobile_phone
      Removed value: -{
-  "description": "Mobile phone",
-  "type": "string"
-}
    • removedInput schema / properties / organization_name
      Removed value: -{
-  "description": "Organization name",
-  "type": "string"
-}
    • removedInput schema / properties / other_phone
      Removed value: -{
-  "description": "Other phone",
-  "type": "string"
-}
    • removedInput schema / properties / present_raw_address
      Removed value: -{
-  "description": "Raw address",
-  "type": "string"
-}
    • removedInput schema / properties / run_dedupe
      Removed value: -{
-  "description": "Enable deduplication. Default false.",
-  "type": "boolean"
-}
    • removedInput schema / properties / title
      Removed value: -{
-  "description": "Title",
-  "type": "string"
-}
    • removedInput schema / properties / typed_custom_fields
      Removed value: -{
-  "description": "Typed custom fields object",
-  "type": "object"
-}
    • removedInput schema / properties / website_url
      Removed value: -{
-  "description": "Website URL",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "body"
+]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the master API key authentication requirement, which is genuine value beyond the annotations. It does not, however, warn that creating without dedupe can produce duplicates -- that risk is only disclosed inside the run_dedupe property description in the schema, not here.

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 prose is a single front-loaded sentence followed by the auth prerequisite -- no wasted words. The trailing pricing HTML comment block is boilerplate noise that adds length without helping an agent invoke the tool, which keeps this from a 5.

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?

An output schema exists, so return-value explanation is not owed. Still, for a destructive, non-idempotent write tool the description omits the duplicate-creation caveat and any pointer to the bulk or update alternatives, leaving behavioral context thinner than the tool's complexity warrants.

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?

The description contributes no parameter information at all; the wrapper 'body' parameter is undocumented in the description. The reported 0% coverage is largely an artifact of only counting top-level parameters, since the 17 nested properties carry rich descriptions and examples (notably run_dedupe). Net effect: the schema does all the work and the description adds nothing, so a middle score is appropriate.

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 states a specific verb and resource: 'Create a new contact.' An agent immediately knows this creates one contact record. However, it does nothing to distinguish itself from close siblings such as post_apollo_contacts_bulk_create (creating many) or patch_apollo_contacts_contact_id (updating an existing one), so the agent must infer the distinction from the names alone.

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?

The only guidance is the prerequisite 'Requires a master API key,' which is useful but not a usage condition. There is no statement of when to use this tool versus bulk_create, the search endpoints, or patch for updates. No alternatives or exclusions are named.

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

All AIsa Sales toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources