Skip to main content
Glama
explorium-ai

Explorium AgentSource MCP Server

Official
by explorium-ai

fetch_prospects

Retrieve prospects (employees) from companies using filters such as job level, department, company size, and location. Returns prospect IDs for targeted sales and marketing outreach.

Instructions

Fetch prospects (employees) using filters such as job level, department, and other professional attributes.

You MUST use the autocomplete tool to retrieve valid values for required filters before calling this tool.

Do NOT call this tool first if you don’t have the necessary filter values.

Returns Prospect IDs for individuals at specific companies.

If a requested filter is not supported by the Explorium API, stop execution and inform the user.

Use fetch_businesses if you're looking for companies instead.

For leadership details at public companies, use enrich_businesses_financial_metrics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoThe page number to return
sizeNoThe number of prospects to return
filtersYes
page_sizeNoThe number of prospects to return per page - recommended: 5
Behavior3/5

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

Without annotations, description carries full burden. It mentions returning Prospect IDs and stopping if filter unsupported, but lacks details on pagination behavior or rate limits.

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?

Front-loaded with purpose, then guidelines and alternatives; every sentence adds value without redundancy.

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?

Given complex nested schema and no output schema, description provides essential guidance but omits explanation of pagination and full return format.

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 75%; description emphasizes autocomplete for certain filters but does not add meaning beyond schema descriptions for page/size 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?

The description clearly states 'Fetch prospects (employees) using filters' and distinguishes from siblings like fetch_businesses and enrich_businesses_financial_metrics.

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 states to use autocomplete tool first and not to call without necessary filter values, providing clear usage context.

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/explorium-ai/mcp-explorium'

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