Outscraper MCP

Official

Overview Schema Source Related Servers Discussions Admin

Yelp Reviews

yelp_reviews

Fetch Yelp reviews from business URLs, with configurable sorting, pagination, and review limits for analysis or extraction. Returns structured review data.

Instructions

Fetch Yelp reviews with the documented /yelp-reviews endpoint.

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	Yelp sort parameter.
`async`	No	Deprecated compatibility flag. Prefer execution_mode.
`query`	Yes	One or more Yelp business URLs.
`cursor`	No	Pagination cursor.
`cutoff`	No	Cutoff value accepted by Outscraper.
`fields`	No	Specific fields to return.
`webhook`	No	Optional webhook URL for async completion.
`reviews_limit`	No	Maximum reviews per query.
`execution_mode`	No	Execution strategy. Use auto to let the MCP server choose between sync and async.

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

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden. 'Fetch' implies a read operation, but it does not disclose pagination behavior, async execution, webhook handling, rate limits, or side effects of parameters like execution_mode and async. This is a substantial gap for a non-trivial scraping tool.

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 a single concise, front-loaded sentence with no wasted words. The phrase 'with the documented /yelp-reviews endpoint' adds little beyond the tool name, but overall the length is appropriate for the little content it conveys.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity — nine parameters, async/sync execution modes, pagination cursor, webhook, and a cutoff parameter — a one-sentence description is not enough for an agent to select and invoke it correctly. The output schema may cover return values, but usage context and behavioral expectations remain largely unexplained.

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?

Schema description coverage is 100%, so the schema already documents all nine parameters. The description adds no parameter-level meaning, but per the rubric the baseline is 3 when the schema covers the parameters; the description neither helps nor harms.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Fetch' and the resource 'Yelp reviews', and the endpoint reference reinforces the operation. It does not explicitly contrast itself with review tools for other platforms, but the resource name makes the core purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use this tool versus siblings like tripadvisor_reviews, google_maps_reviews, or trustpilot_reviews. There are no usage conditions, prerequisites, or exclusion criteria, so an agent must infer applicability solely from the tool name.

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