Skip to main content
Glama
Sign In

Yellow Pages Remote MCP Server

by com.hasdata
OverviewDiscussionsAdmin

yellowpages_place: GET /

hasdata_yellowpages_place_getPlaceDetails
Read-only

Get Yellow Pages Place Details

Scrapes a single YellowPages business listing URL and returns business name, street address, city, region, zip code, coordinates, phone, website, hours of operation, payment methods, categories, ratings, review counts, photos, and service descriptions, plus email and years in business on yellowpages.com listings. Fields the listing does not publish, such as a street address, hours, or email, are omitted from the response. Use to hydrate a lead with verified NAP data, build a B2B contact database from YellowPages URLs collected via the Search endpoint, or validate business legitimacy and hours before outreach.

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": {
      "url": "<url>"
    },
    "name": "hasdata_yellowpages_place_getPlaceDetails"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe YellowPages URL of the place.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, covering the safety/live-data profile. The description adds one genuinely useful behavioral trait: unpublished fields are omitted from the response. However, it says nothing about scraping latency, rate limits, or failure modes for a live scraper, so it adds only modest context beyond annotations.

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-loads purpose, then the field list, then caveats, then use cases in a logical order. The long enumeration of returnable fields is dense but earns its place given there is no output schema. Minor verbosity in the field list.

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?

Given a single-param, no-output-schema scraper with annotations covering safety, the description is nearly complete: it lists returned fields, notes field omission, and gives use cases. It lacks only operational caveats (latency, throttling, bad-URL behavior) that would matter for a live scraper.

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% for the single url parameter, so the schema already documents it and baseline 3 applies. The description restates the URL source (yellowpages.com listings) but adds no format, canonicalization, or validation guidance beyond the schema.

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 (scrapes/returns) and resource (a single YellowPages business listing URL), and enumerates the returned business data fields. Sibling search_getSearchResults is implicitly distinguished by 'a single ... URL' vs. the search endpoint referenced in the usage sentence.

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?

Explicitly names three use cases (hydrate a lead with verified NAP data, build a B2B contact database, validate business legitimacy) and routes the agent to the sibling Search endpoint as the source of URLs. Clear when-to-use with an alternative input source.

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

All Yellow Pages Remote MCP Server toolsInspect
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