Outscraper MCP

Official

Overview Schema Source Related Servers Discussions Admin

Outscraper Business Details

businesses_get

Retrieve full details or selected fields for a known Outscraper business ID after using businesses_search, to enrich or inspect a specific business record.

Instructions

Get one business by Outscraper business id.

Best for:

loading the full detail payload for a business found via businesses_search
fetching a smaller field-selected payload for one known business id

Use this after businesses_search when you already know the exact business id.

Do not use this for discovery:

use businesses_search to find records first
then call businesses_get for the exact item you want to enrich or inspect

Input Schema

TableJSON Schema

Name	Required	Description	Default
`fields`	No	Specific fields to return.
`business_id`	Yes	Outscraper business id returned by /businesses search.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`meta`	Yes
`async`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.2.5Sep 23, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedv0.2.3Aug 1, 2026

TDQS

A4.2/5.0

Behavior3/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 describes the operation as retrieving/fetching data, so behavior is clear. However, it doesn't disclose what 'full detail payload' includes or how fields selection works beyond the schema. It also doesn't mention whether it returns a single object or array. This is adequate but not rich.

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 compact, with key information front-loaded (what it does) followed by usage guidance. Every sentence adds value; no redundancy or fluff.

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?

The tool is simple (2 params, 1 required) and has an output schema, so the description doesn't need to explain return format. The description covers purpose and usage. The only minor gap is not explaining the 'full detail payload' vs field-selected payload, but that's arguably obvious from the fields parameter. Overall complete enough.

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 schema already documents both parameters with descriptions (business_id and fields), and coverage is 100%. The description adds context that business_id comes from businesses_search, which is helpful. No additional parameter semantics are added beyond that, so a baseline 3 is appropriate.

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 retrieves a single business by Outscraper business id and explains the difference from businesses_search, which is for discovery. It specifies the resource (business details) and the verb (get), making it unambiguous and distinct from siblings.

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 instructs when to use this tool (after businesses_search, when business_id is known) and when not to use it (for discovery), referencing the sibling tool businesses_search. This provides clear routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.