Skip to main content
Glama
borgels

mcp-server-apollo

by borgels

Search Companies (Apollo)

apollo_companies_search
Read-onlyIdempotent

Search Apollo for companies by keyword, location, employee count, revenue, domain, or technology. Returns both net-new organizations and saved accounts for CRM deduplication, with pagination.

Instructions

Discover companies via Apollo by keyword tags, name, location (include/exclude), employee-count ranges, revenue range, domains, or technology stack. The response preserves Apollo's split between organizations (net-new) and accounts (already saved to your Apollo team, incl. CRM linkage) — use it to dedupe against your CRM — and passes pagination (page/per_page/total_entries/total_pages) through unchanged. COSTS 1 CREDIT per request (page) that returns results — confirm total credit cost with the user before running multi-page batches. Search records are slim; use apollo_org_enrich for revenue/industry/technology details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
fieldsNoOptional dot-path field projection to shrink the response — only these fields are returned per record. Descends nested objects and maps over arrays, e.g. ["id","name","primary_domain","primary_phone.number"]. Pass ["*"] for the full record.
perPageNoResults per page, 1-100. Defaults to Apollo's default (10).
revenueRangeNoAnnual revenue range in plain integers (no symbols/commas).
organizationIdsNo
qOrganizationNameNoPartial company-name match.
organizationLocationsNoHQ locations to include, e.g. ["Ballerup, Denmark"] or ["Denmark"].
organizationNotLocationsNo
qOrganizationDomainsListNoCompany domains without www. or @.
qOrganizationKeywordTagsNoKeyword tags, e.g. ["plumbing"] or ["pharmaceuticals","biotechnology"].
organizationNumEmployeesRangesNoEmployee-count ranges as "min,max" strings, e.g. ["1,10","101,200"].
currentlyUsingAnyOfTechnologyUidsNoTechnology uids with underscores, e.g. ["wordpress_org"].
Behavior5/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. Description adds credit cost details and response structure (two lists, pagination), going beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four well-structured sentences, no fluff, front-loaded with purpose, followed by response details and cost guidance.

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?

Covers purpose, filter options, response format, credit cost, and references sibling tools. Adequate for a complex search tool with 12 parameters and no output schema.

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 high (75%), and the tool description does not significantly add meaning beyond what the schema already provides for parameters.

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?

Clearly states it discovers companies via multiple filters (keyword tags, name, location, employee ranges, revenue, domains, tech stack). Distinct from sibling enrichment and people search tools.

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?

Explicitly advises using apollo_org_enrich for detailed data, warns about credit cost per page, and recommends confirming costs before multi-page batches.

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/borgels/mcp-server-apollo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server