Skip to main content
Glama
pubrio

Pubrio

Official
by pubrio
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

search_companies

Search B2B companies using filters like name, domain, location, industry, technology, or headcount. Combine with get_locations, search_verticals, and search_technologies for valid codes.

Instructions

Search B2B companies by name, domain, location, industry, technology, or headcount. Tip: use get_locations, search_verticals, and search_technologies to find valid filter codes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default 1)
placesNoComma-separated place names
domainsNoComma-separated list of domains (e.g. "google.com,apple.com")
keywordsNoComma-separated keywords
per_pageNoResults per page (default 25, max 25)
companiesNoComma-separated company domain_search_id UUIDs
locationsNoComma-separated location codes
verticalsNoComma-separated industry verticals
categoriesNoComma-separated technology category IDs
job_titlesNoComma-separated job titles to filter by
revenue_maxNoMaximum revenue
revenue_minNoMinimum revenue
company_nameNoCompany name to search for
technologiesNoComma-separated technologies
employees_maxNoMaximum number of employees
employees_minNoMinimum number of employees
job_locationsNoComma-separated job location codes
linkedin_urlsNoComma-separated LinkedIn company URLs
exclude_fieldsNoComma-separated fields to exclude from response
exclude_placesNoComma-separated place names to exclude
news_galleriesNoComma-separated news gallery names
news_categoriesNoComma-separated news categories
founded_year_endNoFounded year range end
job_posted_datesNoComma-separated job posted dates (YYYY-MM-DD)
news_gallery_idsNoComma-separated news gallery IDs
similarity_scoreNoSimilarity score threshold (0-1)
exclude_locationsNoComma-separated ISO country codes to exclude
founded_year_startNoFounded year range start
vertical_categoriesNoComma-separated vertical category IDs
news_published_datesNoComma-separated news published dates (YYYY-MM-DD)
job_exclude_locationsNoComma-separated job locations to exclude
advertisement_end_datesNoComma-separated ad end dates (YYYY-MM-DD)
vertical_sub_categoriesNoComma-separated vertical sub-category IDs
advertisement_start_datesNoComma-separated ad start dates (YYYY-MM-DD)
advertisement_search_termsNoComma-separated advertisement search terms
is_enable_similarity_searchNoEnable similarity search
advertisement_target_locationsNoComma-separated ad target location codes
advertisement_exclude_target_locationsNoComma-separated ad target locations to exclude

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed28 schema fields changedv1.0.5
    • addedInput schema / properties / advertisement_end_dates
      Added value: +{
+  "description": "Comma-separated ad end dates (YYYY-MM-DD)",
+  "type": "string"
+}
    • addedInput schema / properties / advertisement_exclude_target_locations
      Added value: +{
+  "description": "Comma-separated ad target locations to exclude",
+  "type": "string"
+}
    • addedInput schema / properties / advertisement_search_terms
      Added value: +{
+  "description": "Comma-separated advertisement search terms",
+  "type": "string"
+}
    • addedInput schema / properties / advertisement_start_dates
      Added value: +{
+  "description": "Comma-separated ad start dates (YYYY-MM-DD)",
+  "type": "string"
+}
    • addedInput schema / properties / advertisement_target_locations
      Added value: +{
+  "description": "Comma-separated ad target location codes",
+  "type": "string"
+}
    • addedInput schema / properties / categories
      Added value: +{
+  "description": "Comma-separated technology category IDs",
+  "type": "string"
+}
    • addedInput schema / properties / companies
      Added value: +{
+  "description": "Comma-separated company domain_search_id UUIDs",
+  "type": "string"
+}
    • addedInput schema / properties / exclude_fields
      Added value: +{
+  "description": "Comma-separated fields to exclude from response",
+  "type": "string"
+}
    • addedInput schema / properties / exclude_locations
      Added value: +{
+  "description": "Comma-separated ISO country codes to exclude",
+  "type": "string"
+}
    • addedInput schema / properties / exclude_places
      Added value: +{
+  "description": "Comma-separated place names to exclude",
+  "type": "string"
+}
    • addedInput schema / properties / founded_year_end
      Added value: +{
+  "description": "Founded year range end",
+  "type": "number"
+}
    • addedInput schema / properties / founded_year_start
      Added value: +{
+  "description": "Founded year range start",
+  "type": "number"
+}
    • addedInput schema / properties / is_enable_similarity_search
      Added value: +{
+  "description": "Enable similarity search",
+  "type": "boolean"
+}
    • addedInput schema / properties / job_exclude_locations
      Added value: +{
+  "description": "Comma-separated job locations to exclude",
+  "type": "string"
+}
    • addedInput schema / properties / job_locations
      Added value: +{
+  "description": "Comma-separated job location codes",
+  "type": "string"
+}
    • addedInput schema / properties / job_posted_dates
      Added value: +{
+  "description": "Comma-separated job posted dates (YYYY-MM-DD)",
+  "type": "string"
+}
    • addedInput schema / properties / job_titles
      Added value: +{
+  "description": "Comma-separated job titles to filter by",
+  "type": "string"
+}
    • addedInput schema / properties / linkedin_urls
      Added value: +{
+  "description": "Comma-separated LinkedIn company URLs",
+  "type": "string"
+}
    • addedInput schema / properties / news_categories
      Added value: +{
+  "description": "Comma-separated news categories",
+  "type": "string"
+}
    • addedInput schema / properties / news_galleries
      Added value: +{
+  "description": "Comma-separated news gallery names",
+  "type": "string"
+}
    • addedInput schema / properties / news_gallery_ids
      Added value: +{
+  "description": "Comma-separated news gallery IDs",
+  "type": "string"
+}
    • addedInput schema / properties / news_published_dates
      Added value: +{
+  "description": "Comma-separated news published dates (YYYY-MM-DD)",
+  "type": "string"
+}
    • addedInput schema / properties / places
      Added value: +{
+  "description": "Comma-separated place names",
+  "type": "string"
+}
    • addedInput schema / properties / revenue_max
      Added value: +{
+  "description": "Maximum revenue",
+  "type": "number"
+}
    • addedInput schema / properties / revenue_min
      Added value: +{
+  "description": "Minimum revenue",
+  "type": "number"
+}
    • addedInput schema / properties / similarity_score
      Added value: +{
+  "description": "Similarity score threshold (0-1)",
+  "type": "number"
+}
    • addedInput schema / properties / vertical_categories
      Added value: +{
+  "description": "Comma-separated vertical category IDs",
+  "type": "string"
+}
    • addedInput schema / properties / vertical_sub_categories
      Added value: +{
+  "description": "Comma-separated vertical sub-category IDs",
+  "type": "string"
+}
  2. First observedv1.0.2

TDQS

A3.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only says 'search' without disclosing behavioral traits such as pagination, rate limits, or whether it is read-only. The agent cannot infer side effects or constraints.

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?

The description is two sentences: the first clearly states the tool's purpose, and the second provides a useful tip. No unnecessary words; front-loaded with essential information.

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 tool's complexity with 38 parameters and no output schema, the description is brief and does not explain return format, pagination, or combination rules. The tip is helpful but incomplete for a tool of this scale.

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% with all 38 parameters described, so baseline is 3. The description adds value by advising the use of other tools to obtain valid filter codes, which helps the agent understand parameter values 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?

The description clearly states 'Search B2B companies' with specific criteria (name, domain, location, industry, technology, headcount), differentiating it from sibling search tools focused on people, jobs, or news.

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?

The description includes a tip to use get_locations, search_verticals, and search_technologies to find valid filter codes, guiding the agent on how to prepare inputs. However, it does not explicitly state when to use this tool versus alternatives like search_people.

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

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