Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Yelp business reviews

yelp_reviews_list
Read-onlyIdempotent

Fetch public reviews for a Yelp business using its alias or URL and review category, with cursor support for paginated results.

Instructions

List public reviews for a Yelp business. Requires alias and category. Returns a list (use cursor when paginated).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "alias": "<alias>",
      "category": "<category>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "yelp_reviews_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
aliasYesYelp business alias or full business URL.
cursorNoCursor returned with the previous page.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
categoryYesReview category to return.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds a useful pagination cue ('use cursor when paginated'), but says nothing about ordering, rate limits, or scope beyond 'public' reviews.

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?

Three short, front-loaded sentences with no filler; the core purpose leads and the pagination note follows. Nothing redundant is present.

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?

For a read-only list tool with full schema coverage and safety annotations, the definition covers purpose, required inputs, and pagination adequately. It omits return-shape and ordering details, but with no output schema those are minor gaps rather than blockers.

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?

With 100% schema description coverage, the schema already documents alias, cursor, category enum, and context parameters thoroughly. The description only restates that alias and category are required and that cursor handles pagination, adding no syntax or format detail beyond the structured fields.

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?

States a specific verb and resource ('List public reviews for a Yelp business'), which clearly distinguishes it from list-style siblings serving other sources. It does not explicitly contrast itself with review-summary or histogram siblings, so a 4 rather than 5.

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 conveys required inputs (`alias` and `category`) and pagination usage, which implies the calling context. It offers no explicit when-to-use versus when-not guidance, such as preferring summary or histogram siblings for aggregate data, so alternatives are left to inference.

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

Deploy Server

Other Tools