AIsa Sales

Popular Pages

get_similarweb_popular_pages

Read-onlyIdempotent

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

Input Schema

Name	Required	Description	Default
`limit`	Yes
`domain`	Yes
`offset`	No
`country`	No	Worldwide data only; values are case-insensitive.	ww
`end_date`	Yes
`start_date`	Yes
`web_source`	No
`granularity`	No
`traffic_source`	No
`main_domain_only`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedOct 15, 2026

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."
```
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."
```
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"
+]

Changed18 schema fields changedOct 15, 2026

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."
```
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."
```
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"
+]

Changed18 schema fields changedOct 15, 2026

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."
```
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."
```
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"
+]

First observedSep 15, 2026

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 behavior is usage-based billing (~$0.225 estimate, $0.075/credit), which is genuine but tangential context; it says nothing about rate limits, result caps (limit max 20, offset max 100000) or data freshness.

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?

It is short, but every line is boilerplate pricing markup wrapped in HTML comments rather than front-loaded task information. The space is not earned by anything that helps invoke the tool.

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?

For a 10-parameter, 4-required tool with 10% schema coverage, the description supplies zero functional detail. An output schema exists so return values need not be described, but the complete absence of purpose, usage and parameter context leaves the definition inadequate.

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 10% across 10 parameters, so the description must compensate and it does not — it mentions no parameter at all. Required fields (domain, start_date, end_date, limit), enums for web_source/granularity/country, and the traffic_source semantics are left entirely undocumented.

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 what the tool does. It is entirely a pricing/billing block, so an agent learns nothing about 'popular pages' beyond what the name and title already imply. This is a missing-purpose case rather than a clear one.

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 mention of alternatives among the ~35 similarweb siblings, and no exclusions. The text addresses cost, not selection.

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

All AIsa Sales 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?