Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_search_local

Search Yahoo local business results by query text, including location intent, to get name, category, price range, address, phone, open status, rating, and review count.

Instructions

Search Yahoo local business results. Returns Yahoo's local-business-search results for a query: name, category, price range, address, phone, open status, rating, and review count. Location is resolved from the query text itself, the same way a user would type into Yahoo's own local search box (e.g. "pizza near seattle wa"), not a separate coordinate parameter. Results are fetched from Yahoo's own server-rendered local-search page.

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": {
      "q": "<q>"
    },
    "name": "yahoo_search_local"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query, including any location intent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It clearly explains the location-resolution behavior, the source (Yahoo's server-rendered local-search page), and the return payload fields. It doesn't note auth requirements, pagination, or rate limits, which are common gaps, so it loses a point.

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 appropriately sized for a single-parameter tool and front-loads the core result ('Yahoo local business results') before explaining source and the return fields. Every sentence contributes meaningful information and no redundant restating of the name.

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

Completeness5/5

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

For a one-parameter search tool, the description fully explains how to construct the query, what to expect back, and where the data comes from. There is no output schema but the return fields are enumerated in the text. 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?

The schema covers the single parameter q with its description, and the tool description reinforces that q must include location intent. With 100% schema coverage and one parameter, the description adds meaningful usage context but doesn't need to add more. 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 states the search verb and resource explicitly, and distinguishes this tool from the sibling yahoo_search (its generic counterpart) by specifying local-business-search results and the specific return fields (name, category, price range, address, phone, open status, rating, review count). The scope is unambiguous.

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?

The description explicitly says location is resolved from the query text itself, with an example, rather than a coordinate parameter, and clarifies that queries should be formed like a user typing into Yahoo's local search box. This differentiates it from coordinate-based or separately-parameterized local search tools.

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