Skip to main content
Glama
enrichlayer

Enrich Layer MCP Server

Official
by enrichlayer

enrich_company_search

Read-only

Find companies by location, industry, size, and funding criteria. Returns professional network URLs and supports paginated results for complete search sets.

Instructions

Search for companies by various criteria including location, industry, size, funding, and more. Returns professional network URLs. Cost: 3 credits per URL returned. Returns up to page_size results (max 100) per call. If more matches exist, the response includes total_result_count and a next_page URL — pass its next_token back in to page through the full set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity name (Boolean search), e.g. 'Los Angeles'
nameNoCompany name (Boolean search), e.g. circle || amelex
typeNoType of company.
regionNoState, province, or region (Boolean search), e.g. Maryland OR 'New York'
countryNoISO3166 country code, e.g. US
industryNoIndustry (Boolean search), e.g. technology || manufacturing
page_sizeNoMax results per call (1-100, or 1-10 if enriched), e.g. 10
use_cacheNoCache freshness guarantee.
next_tokenNoPagination cursor for the next page. Omit for the first page. Take the value from the next_token query param inside the previous response's next_page URL. When set, the search filter params are ignored (they are encoded in the token); page_size and enrich_profiles still apply.
descriptionNoCompany description (Boolean search), e.g. navy or naval
specialitiesNoCompany specialities (Boolean search), e.g. innovative product development
enrich_profilesNoReturn complete profile data.
primary_industryNoPrimary industry (Boolean search), e.g. software development
employee_count_maxNoMaximum employee count, e.g. 1000
employee_count_minNoMinimum employee count, e.g. 100
follower_count_maxNoMaximum follower count, e.g. 10000
follower_count_minNoMinimum follower count, e.g. 1000
founded_after_yearNoFounded after this year, e.g. 1985
funding_amount_maxNoMaximum funding amount in USD, e.g. 1000000
funding_amount_minNoMinimum funding amount in USD, e.g. 1000000
founded_before_yearNoFounded before this year, e.g. 2015
funding_raised_afterNoFunding raised after this date (YYYY-MM-DD), e.g. 2019-12-30
funding_raised_beforeNoFunding raised before this date (YYYY-MM-DD), e.g. 2019-12-30
employee_count_categoryNoEmployee count category.
Behavior4/5

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

The description discloses additional behavioral details beyond the readOnlyHint annotation: it mentions a cost of 3 credits per URL returned, pagination via page_size and next_token, and that it returns professional network URLs. This adds transparency about side effects and output characteristics.

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?

The description is concise and well-structured: it starts with the main purpose, then mentions the output type, cost, and pagination. There is no redundant or filler content, making it easy to parse.

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 24-parameter schema and lack of output schema, the description covers cost and pagination but does not explain the structure of the returned company data or the impact of the enrich_profiles parameter. It leaves gaps about what exactly is returned beyond URLs and counts.

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?

The input schema provides descriptions for all 24 parameters (100% coverage). The tool description does not add any additional meaning to the parameters; it only refers to them generally as 'various criteria'. Since schema coverage is high, baseline is 3.

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 the tool searches for companies by various criteria including location, industry, size, funding, and more, and mentions it returns professional network URLs. This distinguishes it from sibling lookup or profile tools that are more specific.

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?

The description implies it is for searching companies by criteria, but does not explicitly state when to use it over alternative tools like enrich_company_lookup or enrich_company_profile. It lacks clear when-to-use or when-not-to-use guidance.

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

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