Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

similarweb_web

Retrieve a domain's web traffic profile—global/country rank, monthly visits, engagement, top countries, sources, keywords, and similar sites—to analyze its audience and competitors.

Instructions

Get SimilarWeb Web Info. Returns SimilarWeb's traffic profile for one domain: global, country and category rank, estimated monthly visits, engagement (bounce rate, pages per visit, time on site), top countries, traffic sources, top keywords and similar sites. DataSource shows whether the full source or the narrower public-page fallback answered; the fallback omits several fields.

Input Schema

NameRequiredDescriptionDefault
domainYesDomain to fetch SimilarWeb data for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose a meaningful behavioral trait: DataSource indicates whether the full source or the narrower public-page fallback answered, and the fallback omits several fields. This warns the agent about partial/degraded results. It does not mention rate limits, auth needs, or failure modes, so it stops short of a 5.

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?

Two tightly packed sentences with the resource named first and the return contents enumerated, followed by the important fallback caveat. No filler, well front-loaded.

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 must describe return values, and it does so comprehensively (rank, visits, engagement, sources, keywords, similar sites) while also flagging the fallback that omits fields. An agent has everything needed to call and interpret it.

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 parameter (domain), and schema coverage is 100%, so the schema already documents it fully. The description's 'for one domain' adds nothing beyond the schema's 'Domain to fetch SimilarWeb data for'. Baseline 3 applies when the schema does the heavy lifting.

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 verb+resource ('Get SimilarWeb Web Info') and immediately enumerates the exact contents of the traffic profile (rank, visits, engagement, countries, sources, keywords, similar sites). This is precise enough to distinguish it from sibling similarweb_search, which is a query-based search rather than a single-domain profile.

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 phrase 'for one domain' implies the single-domain use case, which contrasts with the search-style sibling, but it never explicitly states when to use this tool versus similarweb_search or any alternatives. Usage is implied rather than stated.

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

Deploy Server

Other Tools