Skip to main content
Glama
Sign In

Agent Data API

by io.github.Bustlll
OverviewDiscussionsAdmin

Run one of 70 data tools (Maps, jobs, YouTube, ...)

data_tool_run
Read-onlyIdempotent

Runs one data tool with its JSON input: Google Maps places with contacts, YouTube videos / transcripts / comments, Indeed, LinkedIn and 13 other job boards, LinkedIn companies, Google News and Trends, Google Ads library, TikTok comments, Pinterest, Airbnb, Redfin, AliExpress, app stores, website contacts and SEO checks, sanctions, clinical trials and more. catalog_read what=prices lists every tool with an input example. Each tool has its own price, $0.01-0.08 per capped run (catalog_read what=prices). tier=max runs a bigger job for: google-maps-scraper ($0.35), indeed-jobs-scraper ($0.15), linkedin-company-scraper ($0.15), linkedin-jobs-scraper ($0.12), youtube-comments-scraper ($0.15). Runs live on Apify; 10 s-4 min. Paid with x402 (USDC on Base, Polygon or Solana) per call; failed or empty calls are never 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": {
      "tool": "<tool>",
      "input": "<input>"
    },
    "name": "data_tool_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierNomax = bigger caps, only for the tools listed above.
toolYesTool id from catalog_read what=prices, e.g. google-maps-scraper.
inputYesThe tool's JSON input (see its example in catalog).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare this as read-only, open-world, idempotent, and non-destructive, but the description adds substantial operational context: Apify execution, 10s–4min runtime, x402/USDC payment per call, and that failed or empty calls are never charged. It also documents the higher-cap tier and its specific pricing.

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 core action and catalog dependency are front-loaded, and the pricing/runtime details are useful. The long list of supported domains is somewhat dense, but it efficiently communicates the scope of a 70-tool dispatcher.

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 complex dispatcher with no output schema, the description gives enough to select and invoke it: where to find tool IDs, what input to pass, pricing, runtime, payment, failure behavior, and the max-tier constraint. The only minor gap is that it does not describe the shape of the returned data, though that varies by underlying tool.

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 the baseline is 3, but the description adds useful meaning beyond the schema by saying tool IDs and input examples come from catalog_read what=prices and by enumerating which tools accept tier=max. The input object remains dependent on the catalog, but that is appropriate for a dispatcher.

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 states a specific action — running one data tool with JSON input — and immediately illustrates the breadth of supported tools. It also clearly distinguishes itself from catalog_read, which is the discovery/list operation rather than the execution operation.

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 explicitly points the agent to catalog_read what=prices for tool IDs and input examples, making the prerequisite clear. It also defines when tier=max applies and names the only tools that support it.

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

All Agent Data API 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