Skip to main content
Glama
prospeo-v2

Prospeo MCP Server

Official
by prospeo-v2
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

search_company

Read-only

Search Prospeo's company database with typed filters to find businesses by industry, location, headcount, revenue, funding, and more. Returns up to 25 summaries per page. Requires at least one filter.

Instructions

Search Prospeo's company database using typed filters. Returns up to 25 results per page (max 1000 pages). Costs 1 credit per page that returns results. Each result is a summary (name, website, industry, size, revenue, location, funding, keywords). Pass company_id to enrich_company for the full profile (tech stack, description, job postings, attributes — not included in search). Use filters like company_industry, company_headcount_range, company_location_search, company_technology, company_revenue, company_funding. At least one positive (include) filter is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filtersYesAll company search filters. At least one positive (include) filter is required. Use company_industry, company_headcount_range, company_location_search, company_technology, etc.
pageNoPage number (1–1000). Each page returns up to 25 results.

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Annotations already indicate read-only and non-destructive nature; description adds per-page limits, max pages, credit cost, and result summary detail.

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?

Description is a single, well-structured paragraph with front-loaded purpose, no redundant sentences.

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?

Given the complex filter schema and no output schema, description covers usage, constraints, cost, result summary, and directs to enrich_company for more data.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds context: required include filter, lists common filter names, and states result content, providing value beyond 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?

Description clearly states the tool searches Prospeo's company database with filters, distinguishing it from enrich_company and search_person.

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 mentions requirement for at least one positive filter, credit cost per page, and points to enrich_company for full profiles.

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/prospeo-v2/prospeo-mcp-server'

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