Skip to main content
Glama

AIsa Go-To-Market

SimilarSites

get_similarweb_similar_sites
Read-onlyIdempotent

Usage-based billing; Default request estimate: $0.375 USD (not a fixed price). Declared unit rate: $0.075 USD per similarweb_credit. Account-specific pricing and final settlement may differ.

Input Schema

NameRequiredDescriptionDefault
limitYes
domainYes
offsetNo
countryNoWorldwide data only; values are case-insensitive.ww
end_dateYes
start_dateYes
web_sourceNo
granularityNo
traffic_sourceNo
main_domain_onlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed18 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Two-letter country code. Allowed: us, ww. Default: ww. Coverage is limited to ww and us on the current plan."New value: +"Worldwide data only; values are case-insensitive."
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "us",
      -  "ww"
      -]New value: +[
      +  "ww"
      +]
    • removedInput schema / properties / domain / description
      Removed value: -"Target domain, e.g. example.com."
    • addedInput schema / properties / domain / maxLength
      Added value: +253
    • addedInput schema / properties / domain / minLength
      Added value: +1
    • removedInput schema / properties / end_date / description
      Removed value: -"End month, format YYYY-MM. Together with start_date must span exactly 3 consecutive months, and must be the most recent supported month (the window rolls forward monthly; see the endpoint description)."
    • removedInput schema / properties / granularity / description
      Removed value: -"Time granularity. Allowed: monthly."
    • removedInput schema / properties / limit / default
      Removed value: -20
    • removedInput schema / properties / limit / description
      Removed value: -"Number of rows to return; max 20, billed as 20 if exceeded."
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • removedInput schema / properties / main_domain_only / description
      Removed value: -"Restrict to the main domain only (true/false)."
    • removedInput schema / properties / offset / description
      Removed value: -"Row offset for pagination."
    • addedInput schema / properties / offset / maximum
      Added value: +100000
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • removedInput schema / properties / start_date / description
      Removed value: -"Start month, format YYYY-MM. Must be exactly 2 months before end_date: the window has to span exactly 3 consecutive months within SimilarWeb's latest supported range (see the endpoint description)."
    • removedInput schema / properties / traffic_source / description
      Removed value: -"Traffic-source filter."
    • removedInput schema / properties / web_source / description
      Removed value: -"Traffic source device split. Allowed: desktop, mobile_web, total."
    • changedInput schema / required
      Previous value: -[
      -  "domain",
      -  "start_date",
      -  "end_date",
      -  "limit"
      -]New value: +[
      +  "domain",
      +  "end_date",
      +  "limit",
      +  "start_date"
      +]
  2. Changed18 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Worldwide data only; values are case-insensitive."New value: +"Two-letter country code. Allowed: us, ww. Default: ww. Coverage is limited to ww and us on the current plan."
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "ww"
      -]New value: +[
      +  "us",
      +  "ww"
      +]
    • addedInput schema / properties / domain / description
      Added value: +"Target domain, e.g. example.com."
    • removedInput schema / properties / domain / maxLength
      Removed value: -253
    • removedInput schema / properties / domain / minLength
      Removed value: -1
    • addedInput schema / properties / end_date / description
      Added value: +"End month, format YYYY-MM. Together with start_date must span exactly 3 consecutive months, and must be the most recent supported month (the window rolls forward monthly; see the endpoint description)."
    • addedInput schema / properties / granularity / description
      Added value: +"Time granularity. Allowed: monthly."
    • addedInput schema / properties / limit / default
      Added value: +20
    • addedInput schema / properties / limit / description
      Added value: +"Number of rows to return; max 20, billed as 20 if exceeded."
    • removedInput schema / properties / limit / minimum
      Removed value: -1
    • addedInput schema / properties / main_domain_only / description
      Added value: +"Restrict to the main domain only (true/false)."
    • addedInput schema / properties / offset / description
      Added value: +"Row offset for pagination."
    • removedInput schema / properties / offset / maximum
      Removed value: -100000
    • removedInput schema / properties / offset / minimum
      Removed value: -0
    • addedInput schema / properties / start_date / description
      Added value: +"Start month, format YYYY-MM. Must be exactly 2 months before end_date: the window has to span exactly 3 consecutive months within SimilarWeb's latest supported range (see the endpoint description)."
    • addedInput schema / properties / traffic_source / description
      Added value: +"Traffic-source filter."
    • addedInput schema / properties / web_source / description
      Added value: +"Traffic source device split. Allowed: desktop, mobile_web, total."
    • changedInput schema / required
      Previous value: -[
      -  "domain",
      -  "end_date",
      -  "limit",
      -  "start_date"
      -]New value: +[
      +  "domain",
      +  "start_date",
      +  "end_date",
      +  "limit"
      +]
  3. Changed18 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Two-letter country code. Allowed: us, ww. Default: ww. Coverage is limited to ww and us on the current plan."New value: +"Worldwide data only; values are case-insensitive."
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "us",
      -  "ww"
      -]New value: +[
      +  "ww"
      +]
    • removedInput schema / properties / domain / description
      Removed value: -"Target domain, e.g. example.com."
    • addedInput schema / properties / domain / maxLength
      Added value: +253
    • addedInput schema / properties / domain / minLength
      Added value: +1
    • removedInput schema / properties / end_date / description
      Removed value: -"End month, format YYYY-MM. Together with start_date must span exactly 3 consecutive months, and must be the most recent supported month (the window rolls forward monthly; see the endpoint description)."
    • removedInput schema / properties / granularity / description
      Removed value: -"Time granularity. Allowed: monthly."
    • removedInput schema / properties / limit / default
      Removed value: -20
    • removedInput schema / properties / limit / description
      Removed value: -"Number of rows to return; max 20, billed as 20 if exceeded."
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • removedInput schema / properties / main_domain_only / description
      Removed value: -"Restrict to the main domain only (true/false)."
    • removedInput schema / properties / offset / description
      Removed value: -"Row offset for pagination."
    • addedInput schema / properties / offset / maximum
      Added value: +100000
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • removedInput schema / properties / start_date / description
      Removed value: -"Start month, format YYYY-MM. Must be exactly 2 months before end_date: the window has to span exactly 3 consecutive months within SimilarWeb's latest supported range (see the endpoint description)."
    • removedInput schema / properties / traffic_source / description
      Removed value: -"Traffic-source filter."
    • removedInput schema / properties / web_source / description
      Removed value: -"Traffic source device split. Allowed: desktop, mobile_web, total."
    • changedInput schema / required
      Previous value: -[
      -  "domain",
      -  "start_date",
      -  "end_date",
      -  "limit"
      -]New value: +[
      +  "domain",
      +  "end_date",
      +  "limit",
      +  "start_date"
      +]
  4. First observed

TDQS

D1.3/5.0
Behavior2/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 covered elsewhere. The one piece of added context is billing information (mentioned pricing, per-credit rate, account-specific settlement), which is genuinely useful for a paid external API and is not in the annotations. However, it says nothing about rate limits, latency, data freshness, or failure modes.

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

Conciseness2/5

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

The text is short and formally well-delimited by HTML comment markers, so it is not bloated. But it is entirely boilerplate that does not serve the tool-selection task; 'conciseness' by omission of all substance is under-specification, not efficiency.

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

Completeness1/5

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

Given 10 parameters, 4 of them required, near-zero schema coverage, and a crowded sibling namespace, the description is wholly inadequate. It offers no domain identification, no date-range semantics, no limit/offset behavior, and no indication of what the output contains — an agent cannot call this correctly on the basis of the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 10% (only 'country' is documented, and that is inside the schema, not the description). With 10 parameters — including non-obvious ones like main_domain_only, traffic_source, web_source, and required date-range bounds — the description supplies zero additional meaning, format hints (e.g. date format for start_date/end_date), or defaults.

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

Purpose1/5

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

The description contains no statement of purpose at all — it consists entirely of a pricing block ('Usage-based billing; Default request estimate: $0.375 USD...'). Nothing tells the agent what the tool returns, only that it returns similar sites if you infer that from the tool name. For a 10-parameter analytical tool this is a complete failure to identify verb+resource.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus the many siblings (get_similarweb_ranking, get_similarweb_audience_overlap, get_similarweb_subdomains, etc.). The only 'condition' offered is cost per credit, which does not help the agent decide whether this is the right tool for a task.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources