AIsa Sales

Bulk Create Accounts

post_apollo_accounts_bulk_create

Destructive

Bulk create accounts. Requires a master API key.

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

Input Schema

Name	Required	Description	Default
`body`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 19, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / accounts

Removed value: -{
-  "description": "Array of accounts to create",
-  "type": "string"
-}

removedInput schema / properties / append_label_names

Removed value: -{
-  "description": "Label names to append to each created account",
-  "type": "string"
-}

addedInput schema / properties / body

Added value: +{
+  "properties": {
+    "accounts": {
+      "description": "Array of account attribute objects (maximum 100 accounts per request)",
+      "items": {
+        "properties": {
+          "account_stage_id": {
+            "description": "Account stage/pipeline stage ID (BSON::ObjectId format)",
+            "example": "507f1f77bcf86cd799439014",
+            "type": "string"
+          },
+          "domain": {
+            "description": "Company domain (e.g., 'example.com')",
+            "example": "acme.com",
+            "type": "string"
+          },
+          "facebook_url": {
+            "description": "Facebook page URL",
+            "example": "https://facebook.com/acme",
+            "type": "string"
+          },
+          "hubspot_id": {
+            "description": "HubSpot company ID for CRM integration",
+            "example": "12345678",
+            "type": "string"
+          },
+          "linkedin_url": {
+            "description": "LinkedIn company page URL",
+            "example": "https://linkedin.com/company/acme",
+            "type": "string"
+          },
+          "merged_crm_ids": {
+            "description": "Additional CRM IDs for deduplication",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "name": {
+            "description": "Account name",
+            "example": "Acme Corporation",
+            "type": "string"
+          },
+          "organization_id": {
+            "description": "Apollo organization ID",
+            "example": "507f1f77bcf86cd799439012",
+            "type": "string"
+          },
+          "owner_id": {
+            "description": "Account owner user ID (BSON::ObjectId format). Defaults to current user if not provided",
+            "example": "507f1f77bcf86cd799439013",
+            "type": "string"
+          },
+          "parent_account_id": {
+            "description": "Parent account ID for account hierarchy (BSON::ObjectId format)",
+            "example": "507f1f77bcf86cd799439016",
+            "type": "string"
+          },
+          "phone": {
+            "description": "Company phone number",
+            "example": "+1-555-0135",
+            "type": "string"
+          },
+          "phone_status_cd": {
+            "description": "Phone validation status",
+            "type": "string"
+          },
+          "raw_address": {
+            "description": "Company address",
+            "example": "123 Main St, San Francisco, CA 94105",
+            "type": "string"
+          },
+          "salesforce_id": {
+            "description": "Salesforce account ID for CRM integration",
+            "example": "001pJNj9pix2idKsfj",
+            "type": "string"
+          },
+          "twitter_url": {
+            "description": "Twitter profile URL",
+            "example": "https://twitter.com/acme",
+            "type": "string"
+          },
+          "typed_custom_fields": {
+            "additionalProperties": {
+              "type": "string"
+            },
+            "description": "Custom field values as key-value pairs where key is the field_id and value is the field_value",
+            "example": {
+              "507f1f77bcf86cd799439020": "High Value",
+              "507f1f77bcf86cd799439021": "Q4 2025"
+            },
+            "type": "object"
+          }
+        },
+        "type": "object"
+      },
+      "maxItems": 100,
+      "type": "array"
+    },
+    "append_label_names": {
+      "description": "Array of label names to add to ALL accounts in this request",
+      "example": [
+        "Enterprise",
+        "High Priority"
+      ],
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "run_dedupe": {
+      "default": false,
+      "description": "Enable aggressive deduplication by domain, organization_id, and name. When false (default), only matches by CRM IDs. When true, also matches by domain, organization_id, and name. Existing accounts are returned without modification in both modes",
+      "example": true,
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "accounts"
+  ],
+  "type": "object"
+}

removedInput schema / properties / run_dedupe

Removed value: -{
-  "description": "Enable deduplication. Default false.",
-  "type": "boolean"
-}

changedInput schema / required

Previous value: -[
-  "accounts"
-]New value: +[
+  "body"
+]

First observedSep 15, 2026

TDQS

B3/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 write/safety profile is covered. The description adds two genuinely useful non-schema facts — the master API key requirement and per-request pricing — but says nothing about partial-failure behavior, duplicate handling, or the all-or-nothing nature of a batch mutation.

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?

Two front-loaded sentences carry the core action and the auth prerequisite with no wasted prose. The embedded pricing marker block is boilerplate noise but is clearly delineated and does not bury the substance.

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 values need not be explained, and annotations cover the safety profile. Still missing for a destructive batch mutation: the 100-item limit, whether validation failures abort the whole batch, and what a duplicate match returns — all of which the agent needs before invoking.

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?

The description mentions no parameters at all; its only structured reference is the word "bulk". Reported schema description coverage is 0% at the top level, and the highest-leverage parameter semantics (run_dedupe behavior, the 100-account cap, append_label_names applying to ALL accounts) live only in the nested schema, leaving the description to compensate and it does not.

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 gives a specific verb+resource ("Bulk create accounts"), and "bulk" implicitly distinguishes it from the singular post_apollo_accounts and from post_apollo_accounts_bulk_update. It never names those siblings explicitly, so differentiation is inferable rather than stated.

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 usage-relevant statement is the prerequisite "Requires a master API key". There is no guidance on when to prefer this over post_apollo_accounts (single create), bulk_update, or how to decide on dedupe behavior, and no exclusions or failure conditions are mentioned.

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

All AIsa Sales tools Inspect

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

Need Help?