Skip to main content
Glama
Sign In

Apollo

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Apollo Search Organizations

apollo_search_organizations
Read-onlyIdempotent

Requires a PAID Apollo plan (the free plan answers 403). Search Apollo's company database by industry, headcount, HQ location, technologies used, and funding. BYOK: pass your own Apollo _apiKey (Settings -> Integrations -> API in the Apollo app). Apollo cost: 1 Apollo credit per page of results (up to 100 results/page), billed to your account. Example: apollo_search_organizations({ industries: ["information technology & services"], employee_ranges: ["11,50"], locations: ["San Francisco, California, US"], _apiKey: "your-apollo-key" })

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, default 1.
_apiKeyYesYour Apollo API key. Get one at https://docs.apollo.io/docs/create-api-key.
domainsNoCompany domains, no protocol, e.g. ["apollo.io"].
per_pageNoResults per page, default 10, max 100.
locationsNoCompany HQ locations, e.g. ["San Francisco, California, US"].
industriesNoIndustry names, lowercase, exact match per Apollo's own taxonomy, e.g. ["information technology & services"]. Apollo does not publish a fixed enum via this API — look up exact spellings in the Apollo UI's company filter.
revenue_maxNoMaximum annual revenue, in dollars.
revenue_minNoMinimum annual revenue, in dollars.
keyword_tagsNoKeywords associated with the company.
technologiesNoApollo technology UIDs currently in use, e.g. ["salesforce", "hubspot"]. Apollo supports 1,500+ of these; look them up in the Apollo UI's technology filter rather than guessing.
employee_rangesNoHeadcount ranges as "min,max" strings, e.g. ["1,10", "11,50"].
industry_tag_idsNoApollo industry tag ids, if you already have them (alternative to `industries`).
exclude_locationsNoHQ locations to exclude.
total_funding_maxNoMaximum total funding raised, in dollars.
total_funding_minNoMinimum total funding raised, in dollars.
q_organization_nameNoCompany name, partial match accepted, e.g. "Pipeworx".
latest_funding_date_maxNoLatest most-recent-funding-round date, YYYY-MM-DD.
latest_funding_date_minNoEarliest most-recent-funding-round date, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive/open-world, and the description adds material behavior beyond them: the paid-plan gate with a concrete 403 failure mode, BYOK auth sourcing (Settings -> Integrations -> API), credit cost of 1 per page, and the 100-results-per-page ceiling. That is exactly the billing/auth/limit context annotations cannot express.

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 blocking constraint (paid plan) and prerequisites before capabilities, cost, and example; every sentence carries information. The inline example is somewhat redundant with the schema's own examples, costing a point.

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?

For an 18-parameter search tool this covers eligibility, auth, cost, and filter scope well, and no output schema exists so return values go unaddressed. It hints at pagination via the credit-per-page and 100-results notes but does not describe the response shape, leaving a modest gap.

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 all 18 parameters are already documented in the schema, which sets the baseline at 3. The description adds only a grouped restatement of the filter categories and does not add syntax or format meaning beyond the schema.

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?

Specific verb+resource: 'Search Apollo's company database' with the exact filterable dimensions (industry, headcount, HQ, technologies, funding). The company-database scoping implicitly separates it from apollo_search_people and from the single-record apollo_enrich_organization sibling.

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

Usage Guidelines3/5

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

Gives a real prerequisite (requires a PAID plan; free plan returns 403) and the BYOK requirement, which is genuine when-to-use context. However, it never states when to reach for apollo_enrich_organization or apollo_search_people instead, or any exclusion criteria, so routing between siblings is left to inference.

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

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