Skip to main content
Glama

List live data sources

live_data_sources
Read-only

List ready-made scrapers that turn a site's pages into structured records with fixed fields. Search by site or page kind, then page results with limit and offset.

Instructions

List live data sources: ready-made scrapers that turn one site's pages (a product, a job listing) into records with fixed fields. About a second. Pass query with the site or page kind; page with limit and offset. Leave provider out to search every configured vendor: each row names its provider, and failures names a vendor that could not answer. Each lists its required_inputs and sample_inputs; live_data_source has the full schemas. NOTHING IS CONFIGURED FOR THIS METHOD on this machine, so every call will fail. A key in one of APIFY_TOKEN, BRIGHTDATA_API_TOKEN, NIMBLE_API_KEY, OXYLABS_WEB_API_KEY turns it on: see load_env.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "live_data_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many sources to list. Unset, the backend's page.
queryNoA site, brand or kind of page, e.g. 'amazon product'. Unset, the catalogue in order.
offsetNoHow many to skip first, for the next page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses latency (~a second), the structure of returned rows (`provider`, `required_inputs`, `sample_inputs`), and a `failures` field naming vendors that could not answer. Most importantly it states that nothing is configured on this machine so every call will fail, and names the env vars that enable it plus the `load_env` remedy — exactly the precondition context an agent cannot get from structured fields.

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?

The purpose sentence is front-loaded and the operational warnings follow in a logical order, with no filler. It is dense and slightly run-on, stacking paging, row shape, the disabled-state warning and env vars into a single block, but every sentence carries information.

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 usefully explains what each row contains, and it covers the hard blocker (no vendor configured) plus the fix. The only incompleteness is the dangling `provider` input that does not exist in the schema, leaving a small ambiguity about whether it is a filter argument or only a row field.

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 baseline is 3; the description adds some meaning by framing `query` as a site, brand or page kind and explaining `limit`/`offset` as paging. However it refers to leaving `provider` out, and `provider` is not an input parameter in a schema with additionalProperties:false, which could lead an agent to pass a rejected argument.

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 and resource ('List live data sources') and then defines the resource in concrete terms: ready-made scrapers turning one site's pages into records with fixed fields. It also distinguishes itself from the sibling `live_data_source`, which holds the full schemas, so an agent can pick between the list and the detail view without opening either schema.

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?

Gives concrete invocation guidance: pass `query` with a site or page kind, page with `limit`/`offset`, and omit `provider` to search all configured vendors. It routes the agent to `live_data_source` for schemas and to `load_env` when credentials are missing, but it never states a case where this tool should not be used.

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