xiaoflow mcp server

Get Domain Statistics

get_domain_stats

Read-onlyIdempotent

Retrieve website overview metrics and traffic history for any domain. Choose between domain-specific or brand-level data.

Instructions

Website overview metrics and traffic history. GET /api/v1/websites/:domain?brand=0|1

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": {
      "domain": "<domain>",
      "brand": "<brand>"
    },
    "name": "get_domain_stats"
  }
}

Input Schema

Name	Required	Description
`brand`	Yes	0=domain overview, 1=brand overview.
`domain`	Yes	Domain (e.g. example.com).
`language`	No	Language ID or code.
`location`	No	Geo ID or ISO.

Output Schema

Name	Required	Description
`data`	No	Domain metrics, trends, or keyword records.
`page`	No	Current one-based page.
`error`	No	Human-readable error when success is false.
`total`	No	Total matching domain keywords.
`domain`	No	Normalized domain name.
`success`	Yes	Whether the request completed successfully.
`has_more`	No	Whether another page is available.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 24, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds that it is a GET request and returns metrics/traffic history, but does not disclose any additional behavioral traits (e.g., rate limiting, data freshness, required permissions).

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

Conciseness5/5

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

The description is extremely concise (one sentence plus endpoint) and front-loaded with the most important information. Every word adds value; there is no fluff.

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

Completeness3/5

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

Given the tool has 4 parameters, an output schema, and rich annotations, the description provides a high-level overview but lacks detail on the specific metrics returned or the role of optional parameters (language, location). It is adequate but not comprehensive.

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 baseline is 3. The description mentions 'brand=0|1' and the URL pattern, which reinforces the schema, but does not add new semantic meaning beyond what is in the schema descriptions.

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 clearly states 'Website overview metrics and traffic history' and includes the REST endpoint, which distinguishes it from sibling tools focused on keywords (e.g., get_keyword_metrics, discover_keywords). It specifies the action (get domain statistics) and the resource (domain).

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 usage for retrieving domain overview and traffic data, but does not provide explicit guidance on when to use this tool versus alternatives (e.g., if you need keyword data vs. site metrics). No when-not or exclusions are mentioned.

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

Deploy Server