Skip to main content
Glama
Sign In

Scraper Finder

by com.scraperfinder
OverviewDiscussionsAdmin

Which tool for a website

which_tool
Read-onlyIdempotent

How to get data from one website: its official API (status, name, price and limits notes, docs, check date) beside the ranked catalogue tools (score, price per 1,000 results, core-field coverage, distinctive fields, page and Store link), plus robots.txt and terms facts. Optionally rank by the output fields you need.

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": {
      "website": "<website>"
    },
    "name": "which_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
fieldsNoOptional output fields you need, e.g. ['price', 'bedrooms'].
websiteYesWebsite name, domain or URL, e.g. 'Zillow', 'indeed.com'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds substantive behavioral detail beyond that: it discloses the exact response components (API status, price, limit notes, docs, check date, per-1,000 price, core-field coverage, distinctive fields, page and Store link, robots.txt and terms facts), which is genuinely useful since there is no output schema. It does not state caveats such as what happens when a site has no API, which keeps it short of a 5.

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?

A single front-loaded sentence with the core scope stated first and the detail fields in parentheses. It is dense and parenthetical-heavy but no sentence is wasted; a short lead verb would have improved scanability.

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 no output schema, the description carries the burden of describing return values and does so thoroughly. For a read-only three-parameter lookup tool the remaining omission is routing guidance against siblings, not missing call-critical detail.

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 67%, below the 80% baseline, so the description must compensate. It does clarify that 'fields' is not a filter but a ranking input ('rank by the output fields you need'), which the schema does not convey. The 'limit' parameter remains unexplained beyond its name and bounds, a small residual gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (one website) and enumerates what comes back — official API facts, ranked catalogue tools with scores and pricing, robots.txt and terms facts — so the agent can infer it is a recommendation/lookup tool. However, no explicit verb states what the tool does ('returns a comparison' vs 'recommends'), and the sibling tools list_websites and find_by_field are never mentioned, leaving differentiation implicit.

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?

Usage is only implied by the phrase 'How to get data from one website' and by 'Optionally rank by the output fields you need.' There is no explicit when-to-use statement, no when-not-to-use, and no reference to list_websites (for browsing) or find_by_field (for catalogue search) as alternatives.

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

All Scraper Finder 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