Skip to main content
Glama
Sign In
apollo-io-mcp

apollo-io-mcp

by thevgergroup
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search People

apollo_search_people

Find and target specific people in Apollo's B2B database using advanced filters for roles, locations, seniority, and companies.

Instructions

Search for people in Apollo with advanced filtering options. Use filters to target specific roles, locations, seniority levels, and companies.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "apollo_search_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1)
queryNoSearch query for names, titles, or keywords
filtersNoAdvanced filtering options for targeting specific people
per_pageNoResults per page (1-200, default: 25)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.1

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It only mentions 'advanced filtering options' but does not mention pagination, authentication, rate limits, or whether results are returned. This is a significant gap for a search tool.

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?

Two sentences: first states purpose, second adds usage guidance. No wasted words. Front-loaded with the core action.

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?

Given the complexity (nested filters, 4 parameters, no output schema), the description is incomplete. It lacks details on pagination, result format, and prerequisites. An agent would need to infer behavior from the schema alone.

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%, so the description adds minimal value beyond summarizing filter types. It reiterates 'roles, locations, seniority levels, and companies' which are already in 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?

The description clearly states 'Search for people in Apollo' with a specific verb and resource. It distinguishes from sibling tools like 'apollo_search_companies' and 'apollo_search_news_articles' by focusing on people.

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

Usage Guidelines4/5

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

It gives guidance on using filters for roles, locations, seniority, and companies. However, it does not explicitly state when to use this tool versus alternatives like 'apollo_enrich_person'.

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

Deploy Server

Other Tools