Skip to main content
Glama

Run a live data source (billed)

live_data

Runs a named live data source with supplied inputs to return structured records scraped for the request; use extract when no source covers the page.

Instructions

Run a live data source and get structured records, scraped for this call. Seconds, up to minutes; bills one run at the vendor's rate. Pass the provider live_data_sources named (optional with one vendor configured); inputs come from live_data_source. For a page no source covers use extract. A failed run is an error, never an empty answer. 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

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": {
      "source": "<source>"
    },
    "name": "live_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsNoNamed by the source's input_schema, from `live_data_source`.
sourceYesThe source's name, as `live_data_sources` lists it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.5/5.0
Behavior4/5

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

Beyond annotations (openWorld=true, idempotent=false, not read-only), it discloses cost model ('bills one run at the vendor's rate'), latency ('Seconds, up to minutes'), and failure semantics ('A failed run is an error, never an empty answer') — all material for a billed, non-idempotent call. The one gap is that expiry/retention of scraped records or vendor rate specifics are not described.

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 and dense with no filler: scope, cost, sourcing, alternative, failure mode, prerequisites. Occasional garbling ('Pass the `provider` `live_data_sources` named') and the all-caps environment warning slightly hurt readability but the critical facts still land first.

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 two-parameter, billed, open-world tool it covers cost, latency, sourcing, alternatives, error behavior, and setup prerequisites. With no output schema, however, it says only 'structured records' without describing record shape or how large result sets come back, leaving that to inference.

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 earns an extra point by stating where values come from (`live_data_sources` names the source, `live_data_source` supplies `inputs`) and that the source argument is optional when one vendor is configured. It loses a point for calling the argument `provider` while the schema names it `source`, a mismatch that could cause a malformed call.

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 ('Run a live data source and get structured records, scraped for this call') and explicitly separates itself from sibling `extract` for pages no source covers. The title's billing marker is reinforced in text, so an agent knows exactly what class of action this is.

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?

Gives explicit use conditions (a page covered by a configured source), the routing rule when that condition fails ('For a page no source covers use `extract`'), and the prerequisite path (API key in one of the named env vars, see `load_env`). It even warns that on this machine every call will fail until a key is set.

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