AIsa Domain & Keyword Research

DataForSEO Labs Status

get_dataforseo_labs_status

Read-onlyIdempotent

‌ By calling this endpoint, you will find out when the DataForSEO Labs data was last updated. The API response will provide separate update dates for the Google, Bing, and Amazon endpoints of DataForSEO Labs API.

Usage-based billing; Default request estimate: $0.012 USD (not a fixed price). Account-specific pricing and final settlement may differ.

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": "get_dataforseo_labs_status"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026
- addedOutput schema / x-fastmcp-wrap-result
```
Added value: +true
```
Changed1 schema field changedOct 15, 2026
- removedOutput schema / x-fastmcp-wrap-result
```
Removed value: -true
```
Changed1 schema field changedOct 15, 2026
- addedOutput schema / x-fastmcp-wrap-result
```
Added value: +true
```
First observedSep 15, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds useful return-shape context (separate update dates per Google/Bing/Amazon) but says nothing about auth, rate limits, or cost behavior beyond the boilerplate pricing block.

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 functional content is two front-loaded sentences with no waste. The 'By calling this endpoint' lead-in is slightly filler, and the appended pricing boilerplate adds length, but the useful information comes 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 no-parameter, read-only status endpoint with an output schema and full annotation coverage, the description supplies what is needed. The output schema handles the return payload, and the description briefly previews its structure; nothing essential is missing.

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?

Zero parameters with 100% schema coverage, so the baseline is 4. There is no parameter semantics to explain, and the description correctly does not invent any.

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

Purpose4/5

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

States a specific verb+resource: discover when DataForSEO Labs data was last updated, and even names the three endpoint families (Google, Bing, Amazon) covered. It is clear what the tool returns, but it does not distinguish itself from sibling status/metadata tools such as get_dataforseo_labs_available_filters or get_dataforseo_labs_google_available_history.

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?

There is no explicit when-to-use guidance, no preconditions, and no routing to alternatives. The agent can infer this is a freshness/health check, but nothing tells it when checking status is warranted versus simply calling the data endpoint directly.

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

All AIsa Domain & Keyword Research tools Inspect

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

Need Help?