Skip to main content
Glama

Crawlora MCP

yelp_business_photos

Read-only

Fetch a Yelp business's public photo gallery by alias or encoded ID without login or cookies. Use yelp_business_reviews for review text or yelp_business_menu for menu data.

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": {
      "id": "<id>",
      "limit": "<limit>",
      "offset": "<offset>"
    },
    "name": "yelp_business_photos"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesYelp business alias or encoded id
limitYesMax photos to return, 1-50
offsetYesPagination offset

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"Yelp business alias or encoded id"
    • addedInput schema / properties / limit / description
      Added value: +"Max photos to return, 1-50"
    • addedInput schema / properties / offset / description
      Added value: +"Pagination offset"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint, openWorldHint), and the description adds the meaningful operational detail that the gallery is public and requires no login or cookies. That is genuine context beyond the structured fields; return format is covered by the output schema.

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 tight sentences, front-loaded with the primary action and resource, followed by a compact routing clause. Zero filler.

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?

With an output schema present and annotations declaring the read/no-auth profile, the description carries all the selection-relevant information an agent needs. Nothing essential is missing.

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 coverage is 100%, so the schema already documents id, limit, and offset. The description restates the alias/encoded-ID distinction for id but adds no new syntax or format detail. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb (Fetch), resource (a Yelp business's public photo gallery), and scope (by alias or encoded ID), and explicitly distinguishes itself from yelp_business_reviews and yelp_business_menu. An agent can select this tool without ambiguity.

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

Usage Guidelines4/5

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

Explicitly routes the agent to sibling tools for review text and menu data, which implies this tool is for photos only. Clear context, but it doesn't state when-not to use this tool beyond the two named alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources