SiteCheck Company Records

Yellow Pages business listings for a search term

b2b_yellowpages

Read-only

Yellow Pages (US) business listings for a search term and location: name, phone, street address, city/state/ZIP, categories, star rating and review count (where shown), years in business, website and YP listing link. Up to 30 per page, page 1 to 10. From yellowpages.com's public search through a residential proxy. Related tools on this server, for a different need: b2b_bbb when you need Better Business Bureau search: finds businesses by name; b2b_manta when you need Manta US small-business directory search by keyword. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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>",
      "location": "<location>"
    },
    "name": "b2b_yellowpages"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	What to search for, e.g. 'plumber', 'dentist', 'pizza'
`page`	No	Results page 1 to 10 (default 1)
`location`	Yes	City and state or ZIP, e.g. 'Austin, TX' or '78704'

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Beyond readOnlyHint/openWorldHint, it discloses provenance (yellowpages.com public search via a residential proxy), result ceilings (30 per page, pages 1–10), and the billing model including the important detail that failed calls are not charged. It does not discuss rate limits, throttling, or empty-result behavior, so it stops short of the top score.

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?

Front-loaded with the resource and returned fields, then pagination, then sibling routing, then price — a sensible ordering with no filler sentences. The returned-field enumeration is long and partially duplicates the output schema, which keeps it from being maximally tight.

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 paid, open-world read tool with an output schema and full param coverage, the description covers scope, cost, provenance and alternatives adequately. Minor gaps remain around failure modes (no results, proxy errors) and whether pagination beyond 10 is possible, but nothing essential to correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description adds a small amount beyond the schema by tying the query/location pair to a US-local-search model and restating the page 1–10 bound alongside the 30-per-page volume. It gives no additional syntax guidance for location beyond what the schema examples already show.

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 names a specific verb+resource (Yellow Pages US business listings search) and enumerates exactly what comes back: name, phone, address, categories, rating, review count, years in business, website and listing link. It also explicitly contrasts itself with the named siblings b2b_bbb and b2b_manta, so an agent can discriminate without opening a schema.

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?

It routes the agent explicitly: use this for yellowpages.com consumer-style local search, use b2b_bbb for Better Business Bureau name lookups, use b2b_manta for Manta keyword search. Each alternative comes with the condition that selects it, leaving nothing to inference.

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

All SiteCheck Company Records tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?