Sliq

Apollo enrich

apollo_enrich

Read-only

Pass all candidate domains at once — one call with the full list, not one call per domain. The tool fans them out to Apollo's /organizations/enrich endpoint in parallel (ThreadPoolExecutor, max 20 concurrent, well within Apollo's 1000 req/min limit), so a batch costs one tool round instead of N.

Org-only (company domains, not people). For person enrichment (work email, LinkedIn URL), use find_email instead.

Costs 1 Sliq credit per found=True result (free for found=False, free on BYO Apollo). Soft-fails on insufficient credits — already- enriched results are still returned.

Per-user 24h cache: any domain this user already enriched — in an earlier run_code sandbox, an earlier call, or an earlier run — is served from cache with no second Apollo call and no second charge (both found=True and found=False are cached). The input list is also deduped by canonical form before fan-out.

Each enriched company is also saved to your canonical company entities, queryable via query_companies. List of dicts, one per input domain, in the same order. Each is either: {found: True, name, domain, industry, employee_count, annual_revenue, founded_year, latest_funding_stage, total_funding, location, linkedin_url, description} OR: {found: False, queried_domain, message}

latest_funding_stage is Apollo's title-case display string (e.g. "Seed", "Series A", "Series B", ..., "Series Unknown", "Private Equity", "Post-IPO Equity", "Other") — passed through verbatim, NOT a lowercase_underscore enum. It is None/absent when Apollo has no funding data for the org. total_funding is a USD integer (Apollo defaults it to 0, not null, when absent). Apollo's funding coverage is patchy, especially for bootstrapped / PE-owned / privately-held companies. Callers gating on these fields should decide how to handle missing data — matches_icp includes-on-null rather than excludes, so legit rows with thin Apollo coverage aren't silently dropped, and normalizes case + separators when comparing the stage string.

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": {
      "domains": "<domains>"
    },
    "name": "apollo_enrich"
  }
}

Input Schema

Name	Required	Description	Default
`domains`	Yes	List of company domains (e.g. ["acme.com", "foo.io"]). Order is preserved in the return list. Duplicates (after canonicalization) are collapsed and the result is shared.
`on_behalf_of`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

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."

Changed1 schema field changedOct 19, 2026

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."
+}

First observedSep 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Goes far beyond the single readOnlyHint annotation: credit cost model (1 credit per found=True, free on BYO Apollo), soft-fail on insufficient credits with partial results retained, 24h per-user cache behavior, parallel fan-out with concurrency limits, and the side effect of persisting companies to canonical entities. Minor deduction because it does not acknowledge the tension with readOnlyHint=true — the call spends credits and creates persistent company records, which the agent may not expect from a 'read-only' tool.

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?

Front-loaded with the core action and batch instruction, then cost, cache, and output behavior in scannable blocks. It is long, but the length is driven by genuinely decision-relevant content (cost, cache, funding-field caveats); the XML-style tags and a few redundant restatements of dedupe keep it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the embedded <returns> section carries the burden and does it well: per-domain dict shape for both found=True and found=False, field-level caveats on `latest_funding_stage` (title-case passthrough, not an enum) and `total_funding` (0 rather than null), plus how `matches_icp` handles nulls. Nothing an agent needs to call or interpret results is missing.

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% and the schema already documents order preservation, dedupe of canonicalized duplicates, and `on_behalf_of` semantics. The description largely restates the dedupe/ordering facts rather than adding syntax or format guidance (e.g., whether bare domains with paths or URLs are accepted), so 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?

States a specific verb, resource and scope: 'Enrich multiple company domains in a single call', explicitly org-only, and names the sibling to use instead for people (`find_email`). An agent can distinguish it from `enrich_linkedin_profiles`, `find_email`, and `apollo_search` without opening any schema.

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 explicit batch guidance ('Pass all candidate domains at once — one call with the full list, not one call per domain') and an explicit exclusion with the alternative named ('Org-only ... For person enrichment ... use `find_email` instead'). When-to-use and when-not-to-use are both covered.

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

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