Skip to main content
Glama
outscraper

Outscraper MCP

Official
by outscraper

Outscraper Businesses Search

businesses_search

Search normalized business records using structured filters, natural-language queries, or both. Build lead lists with cursor pagination and field selection for targeted discovery.

Instructions

Search Outscraper businesses using structured filters, a natural-language query, or both.

Best for:

  • building lead lists from normalized business records

  • filtering by country, state, city, type, and other structured business fields

  • paginated browsing with cursor when you want repeatable result navigation

Prefer this tool when:

  • you already know the geography, categories, or other business filters you want

  • you want the normalized /businesses dataset rather than raw Google Maps search behavior

  • you need stable field selection and cursor-based pagination

Use this instead of google_maps_search when:

  • you want the normalized /businesses API

  • you need field selection, filters, or cursor pagination

Note:

  • according to the current OpenAPI, /businesses is a synchronous endpoint in this MCP server

  • async-style execution controls are intentionally not exposed here

  • structured filters are the most reliable input mode

  • live Outscraper testing showed that free-form query parsing may fail with "Could not parse query into a valid request format."

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoResult page size.
queryNoOptional natural-language business search query parsed by Outscraper.
cursorNoPagination cursor from the previous response.
fieldsNoSpecific fields to return for each business.
filtersNoStructured Outscraper /businesses filters JSON.
include_totalNoWhether Outscraper should include total matching count.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
metaYes
asyncNo
Behavior5/5

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

Even without annotations, the description discloses important behavioral traits: the /businesses endpoint is synchronous in this MCP server, async-style execution controls are intentionally not exposed, structured filters are more reliable than free-form queries, and live testing showed query parsing may fail with a specific error. This goes well beyond typical descriptions.

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 well-structured with a lead sentence followed by labeled bullet sections. Each sentence serves a distinct purpose: clarifying scope, usage context, differentiation, and caveats. No fluff or redundancy.

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 tool's complexity (6 params, nested filters, no required params, output schema present), the description covers all essential decision factors: when to use, differentiators from alternatives, pagination behavior, and known failure modes. It is sufficiently complete for an agent to select and invoke correctly.

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?

The input schema provides 100% coverage with descriptions for all 6 parameters, so the baseline is 3. The description adds value by warning that free-form query parsing may fail and recommending structured filters as the most reliable input mode, giving practical parameter guidance 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 opens with a specific verb and resource: 'Search Outscraper businesses using structured filters, a natural-language query, or both.' It clearly distinguishes this tool from google_maps_search by highlighting the normalized /businesses dataset and cursor-based pagination.

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?

The description provides explicit 'Best for', 'Prefer this tool when', and 'Use this instead of google_maps_search when' sections. This gives unambiguous guidance on when to choose this tool over its sibling, including context like building lead lists and needing stable field selection.

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

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