Skip to main content
Glama
Sign In

Agent Data API

by com.chiemgaufilms.agent
OverviewDiscussionsAdmin

traffic_estimate

Idempotent

Estimated monthly organic and paid Google traffic for up to 10 domains in one call (DataForSEO Labs Bulk Traffic Estimation). Returns: JSON with domains, not_found. PAID: 0.04 USDC per call (USDC on eip155:8453, x402 v2). Requires an x402-capable MCP client that attaches the payment in _meta["x402/payment"] (e.g. createx402MCPClient from @x402/mcp). Without a payment this tool returns a "payment required" result and charges nothing.

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": {
      "domains": "<domains>"
    },
    "name": "traffic_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesDomains to estimate: 1 to 10 entries, e.g. example.com. Duplicates removed.
language_codeNoLanguage code such as en or de. Default: English if available for the country, else its first language. Unsupported country/language pairs are refused before payment.
location_codeNoDataForSEO location code. Country level: 2840 = United States (default), 2276 = Germany, 2040 = Austria, 2756 = Switzerland. Google SERP, Maps, News, Images and Local Market Check also accept city/region codes in Germany, Austria and Switzerland (free lookup: GET /api/v1/locations?q=...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / location_code / description
      Previous value: -"DataForSEO country code. 2840 = United States (default), 2276 = Germany, 2826 = United Kingdom. Country-level codes only."New value: +"DataForSEO location code. Country level: 2840 = United States (default), 2276 = Germany, 2040 = Austria, 2756 = Switzerland. Google SERP, Maps, News, Images and Local Market Check also accept city/region codes in Germany, Austria and Switzerland (free lookup: GET /api/v1/locations?q=...)."
  2. Added

TDQS

A4.2/5.0
Behavior5/5

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

Adds substantial behavioral context beyond annotations: exact cost (0.04 USDC), payment mechanism, required client capability, and the no-payment fallback behavior that returns 'payment required' and charges nothing. This is exactly the kind of paid-tool transparency an agent needs before invoking it.

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 is front-loaded and the remaining sentences cover returns and payment prerequisites without obvious fluff. The payment details are dense but necessary for a paid tool; overall it is appropriately sized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description names the return shape (domains, not_found), cost, payment path, and non-payment result. Combined with a fully documented input schema, an agent has enough information to call it correctly.

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%, so the schema already documents domains, language_code, and location_code thoroughly. The description reinforces the 10-domain limit and mentions return fields, but adds little parameter-level meaning beyond what the schema provides.

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 resource and scope: estimated monthly organic and paid Google traffic for up to 10 domains in one call. The bulk scope and traffic-specific output distinguish it from single-domain siblings such as domain_overview without needing to name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the bulk use case by saying 'up to 10 domains in one call' and clearly states the x402 payment prerequisite. However, it does not explicitly say when to use this instead of a sibling tool or when not to use it, so guidance is present but implied rather than explicit.

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