Skip to main content
Glama
Sign In

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Apollo save

apollo_save
Destructive

Save people as contacts or companies as accounts in the user's Apollo CRM, where they show in Apollo's web UI. Confirm with the user before calling this tool.

Each contact needs an email; it's the only required field. For a contact whose email you don't have, get it with find_email first, passing an apollo_search result's name and apollo_id, or the person's full name and company. Then save the real name and email it returns as {first_name, last_name, email, title, organization_name}.

For accounts, the result splits the count into "created" (new rows) and "existing" (already in the CRM — Apollo dedupes by domain); "saved" is their sum, so a re-save reads as saved == requested rather than a false failure.

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": {
      "type": "<type>",
      "items": "<items>"
    },
    "name": "apollo_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes"contacts" or "accounts"
itemsYesList of dicts. For contacts: {first_name, last_name, email (required), title, organization_name}. For accounts: {name, domain}.
sequence_idNoOptional. If provided, contacts will also be added to this Apollo sequence for outreach.
on_behalf_ofNoA teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / on_behalf_of / description
      Previous value: -"An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."New value: +"A teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
  2. Changed1 schema field changed
    • addedInput schema / properties / on_behalf_of
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / items / description
      Previous value: -"List of dicts. For contacts: {first_name, last_name, email (REQUIRED), title, organization_name}. For accounts: {name, domain}."New value: +"List of dicts. For contacts: {first_name, last_name, email (required), title, organization_name}. For accounts: {name, domain}."
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare a non-read, destructive write, and the description goes well beyond them by disclosing dedupe behavior ('Apollo dedupes by domain'), the created/existing/saved split, and the human-confirmation requirement. It does not mention credit consumption or rate limits for a CRM write, which keeps it short of a 5.

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?

Three short paragraphs, front-loaded with the core action and the confirmation rule, then the contact workflow, then the account result semantics. Dense with useful detail and no filler, though the contact field list duplicates the schema.

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?

With no output schema, the description correctly explains how to interpret the account result (created + existing = saved, so a re-save shows saved == requested). The main remaining gap is that it never explains the returned shape for contact saves, which is the more common call.

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 baseline is 3, and the description mostly restates the schema's item shapes. It does add one genuinely new constraint not visible in the schema — that email is the only required contact field, since the nested item object has no required list — but says nothing further about sequence_id or on_behalf_of beyond what the schema documents.

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?

States a specific verb and two concrete resources ('Save people as contacts or companies as accounts in the user's Apollo CRM') and adds the observable effect ('where they show in Apollo's web UI'). This clearly separates it from read-side siblings such as apollo_search, apollo_enrich, and query_people.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition ('Confirm with the user before calling this tool') and an explicit fallback path: when a contact email is missing, call find_email first using an apollo_search result's name and apollo_id. The when-to-use and when-to-do-something-else cases are both named.

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

All Sliq 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