SiteCheck Company Records

Similarweb traffic overview for a domain: global, country

b2b_similarweb

Read-only

Similarweb traffic overview for a domain (public page data, last full month): global, country and category rank, monthly visits and change, 3-month trend, bounce rate, pages per visit, visit duration, traffic sources, top countries, age and gender split, organic vs paid search, top keywords and social networks, similar sites and company facts. From similarweb.com via a stealth proxy. Takes about 15 s; allow a 45 s timeout. Related tools on this server, for a different need: b2b_bbb when you need Better Business Bureau search: finds businesses by name; b2b_bizquest when you need businesses for sale on BizQuest: listing title, short. Price: $0.05 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not 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": {
      "domain": "<domain>"
    },
    "name": "b2b_similarweb"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Website domain, e.g. google.com, shopify.com

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial behavioral context beyond them: data freshness (last full month), provenance (similarweb.com via a stealth proxy), expected latency (~15 s, allow a 45 s timeout), and billing terms ($0.05 USDC via x402 on Base/Solana/Arc, failed calls not charged). These are exactly the operational facts an agent needs before committing to a slow, paid call.

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?

Front-loaded with the highest-value information (what data, how fresh) before cost and latency. The long comma-separated metric list is dense but earns its place by defining coverage; a slightly tighter phrasing of the sibling/pricing tail would improve it.

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?

For a single-parameter, paid, slow external scrape with an output schema already defining return values, the description covers everything material: freshness, source mechanism, latency/timeout, cost model, and failure billing. Nothing an agent needs to invoke it correctly is missing.

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% with a single required 'domain' parameter already exemplified in the schema. The description reinforces the scope ('for a domain', 'public page data') but adds no format rules, normalization guidance, or URL-vs-domain handling beyond what the schema states, so it is a baseline case.

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 opens with a specific verb+resource+scope: 'Similarweb traffic overview for a domain (public page data, last full month)'. It then enumerates the concrete metrics returned (visits, rank, bounce rate, traffic sources, demographics, keywords, similar sites), so an agent can tell exactly what this tool produces versus any other sibling on the server.

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

Usage Guidelines4/5

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

It explicitly routes the agent away for different needs by naming alternatives and their conditions ('b2b_bbb when you need Better Business Bureau search', 'b2b_bizquest when you need businesses for sale'). The trigger for this tool (traffic/audience data for a single domain, last full month) is clear, though there is no explicit statement of when-not-to-use or what a non-public/undiscoverable domain yields.

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

All SiteCheck Company Records 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?