Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Yelp business details

yelp_business_get
Read-onlyIdempotent

Fetch public Yelp business details using its alias or full business URL to support research, validation, and local business lookups.

Instructions

Get public details for a Yelp business. Requires alias.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "yelp_business_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
aliasYesYelp business alias or full business URL.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds almost no behavior beyond that: "public" hints that only public data is returned, but nothing is said about rate limits, error behavior on unknown aliases, or response shape. With the annotation bar lower, this still adds essentially nothing new.

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?

Two short sentences with zero filler, and the core action is front-loaded before the parameter requirement. Nothing in the text is redundant within the description itself.

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?

For a simple read-only lookup with a fully documented schema and complete annotations, this is adequate but thin. It omits any indication of what "details" includes or how an unknown/ambiguous alias behaves, though the schema covers the unusual context and conversation_id handshake requirements.

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%, including alias accepting either an alias or a full business URL, plus the context/llm_model/conversation_id conventions. The description only repeats that alias is required, adding no new meaning; baseline 3 applies when the schema carries the semantics.

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?

"Get public details for a Yelp business" states a specific verb (get) and resource (Yelp business), which distinguishes it from list-oriented siblings like yelp_businesses_search and yelp_reviews_list. It stops short of naming an alternative or stating which fields constitute "details," so it is clear but not fully differentiating.

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 only guidance is "Requires `alias`," which is a prerequisite already encoded in the schema's required array. There is no statement of when to use this tool versus yelp_businesses_search or yelp_business_photos_list, and no exclusions or conditions given.

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