Skip to main content
Glama

seodraft

by app.seodraft
OverviewDiscussionsAdmin

DataForSEO status

dataforseo_status
Read-only

Whether DataForSEO is connected, the account balance in USD (balanceUsd and totalUsd, rounded to cents), and what seodraft has already spent from it: spentTotal and spentLast30d in USD at thousandth-of-a-dollar precision, with httpRequestsTotal and httpRequestsLast30d counting the paid HTTP requests behind that spend (one metrics batch is three requests). Also returns rates, the per-endpoint price map used for estimates, and rateSources, saying for each endpoint whether that price came from the account's own rate card or the public list; there is no platform DataForSEO account, credentials are always the user's own. measurementAvailable answers whether this workspace can measure anything: false without credentials or when the account lookup fails, returned degraded: true with reason missing-credentials, the same refusal add_topics gives. Free to call. Never returns the password. signals is the stored topic bank in the observed/unavailable vocabulary: topics, queriesChecked, reportedVolume (0 counts), aiVolumeSignal (above zero only), aiOverviewFound, relatedQuestions, unmeasured, complete (every topic answered for) and noVolumeReported (no topic carries a reported volume, normal for long-tail questions). limits returns perRunUsd, perDayUsd and windowHours, the ceilings the next paid call is checked against, and spentLast24h is what has already been spent inside that rolling window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdNoThe workspace this call acts on, as listed by list_workspaces. Left out, the call uses the workspace the account is in right now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspaceId
      Added value: +{
+  "description": "The workspace this call acts on, as listed by list_workspaces. Left out, the call uses the workspace the account is in right now.",
+  "type": "string"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior5/5

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

With readOnlyHint/destructiveHint already covering safety, the description still adds a lot: credentials are always the user's own with no platform account, the password is never returned, 'free to call', and measurementAvailable=false degrades with reason missing-credentials mirroring add_topics. These are concrete behavioral facts an agent cannot get from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the connectivity answer, but the body is a single semicolon-chained run-on packing rate maps, rateSources, signal vocabulary and limits into one breath. It is dense and hard to scan, though for a tool with no output schema most of that content is load-bearing.

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?

There is no output schema, so the description carries the full return-value burden and does so thoroughly — field-by-field meaning of balance, spend, signals vocabulary, limits and spentLast24h. An agent has everything needed to interpret the response.

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?

Only one optional parameter (workspaceId) and schema coverage is 100%, so the schema already documents it fully, including the current-workspace default. The description's 'this workspace' phrasing adds nothing beyond the schema; baseline 3.

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?

The description states a specific resource — DataForSEO connection status plus account balance, spend, rates and limits — with concrete field names (balanceUsd, spentLast30d, measurementAvailable). It is unambiguous what the tool is, but it never explicitly distinguishes itself from siblings (e.g. refresh_metrics, check_ai_access), which all touch related measurement concepts.

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?

'Free to call' is useful cost guidance, and the degraded/missing-credentials clause hints at when the answer is unusable, but there is no explicit statement of when to call this versus a sibling or what to do with the result. Usage is only implied.

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

All seodraft 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