Skip to main content
Glama

AIsa Similarweb

by one.aisa
OverviewDiscussionsAdmin

Deduplicated Audience

get_similarweb_deduplicated_audience
Read-onlyIdempotent

Usage-based billing; Default request estimate: $0.525 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
domainYes
countryNoWorldwide data only; values are case-insensitive.ww
end_dateYes
start_dateYes
web_sourceNo
granularityNomonthly
main_domain_onlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 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."
    • removedInput schema / properties / granularity / description
      Removed value: -"Time granularity. Allowed: monthly. Default: monthly."
    • removedInput schema / properties / main_domain_only / description
      Removed value: -"Restrict to the main domain only (true/false). Default: True."
    • removedInput schema / properties / start_date / description
      Removed value: -"Start month, format YYYY-MM."
    • 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"
-]New value: +[
+  "domain",
+  "end_date",
+  "start_date"
+]
  2. Changed11 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."
    • addedInput schema / properties / granularity / description
      Added value: +"Time granularity. Allowed: monthly. Default: monthly."
    • addedInput schema / properties / main_domain_only / description
      Added value: +"Restrict to the main domain only (true/false). Default: True."
    • addedInput schema / properties / start_date / description
      Added value: +"Start month, format YYYY-MM."
    • 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",
-  "start_date"
-]New value: +[
+  "domain",
+  "start_date",
+  "end_date"
+]
  3. Changed11 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."
    • removedInput schema / properties / granularity / description
      Removed value: -"Time granularity. Allowed: monthly. Default: monthly."
    • removedInput schema / properties / main_domain_only / description
      Removed value: -"Restrict to the main domain only (true/false). Default: True."
    • removedInput schema / properties / start_date / description
      Removed value: -"Start month, format YYYY-MM."
    • 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"
-]New value: +[
+  "domain",
+  "end_date",
+  "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. The description's only added behavioral fact is cost: usage-based billing at ~$0.075 per similarweb_credit with a ~$0.525 default request estimate, which is genuinely useful non-schema context. However, nothing is said about the data semantics of 'deduplicated' audience, date-range constraints, or latency, so it falls short of a 3.

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, but it is not concise in the useful sense: 100% of the content is billing boilerplate wrapped in HTML comment markers, and none of it is front-loaded functional information. It earns no place toward tool selection.

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?

An output schema exists, so return values need not be described, but for a 7-parameter, 3-required analytics tool the description supplies no purpose, no usage context, and no parameter semantics. The definition is effectively incomplete for correct invocation.

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 only 14%, and the description adds zero parameter meaning. Three required parameters (domain, start_date, end_date) and four optional ones (web_source, main_domain_only, granularity, country) are left entirely unexplained in prose, so an agent must guess at date formats and what 'deduplicated' implies for the domain argument.

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 never states what the tool does. It contains only a pricing/billing block ('Usage-based billing; Default request estimate: $0.525 USD...'), which gives an agent no way to know this returns a deduplicated audience metric for a domain, let alone how it differs from siblings like get_similarweb_audience_overlap or get_similarweb_demographics.

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 when-to-use guidance, no exclusions, and no reference to any alternative tool. With ~35 similarweb siblings, the absence of routing guidance is a severe gap.

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

All AIsa Similarweb 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