AIsa Sales

Top Sites Ranking

get_similarweb_top_sites_ranking

Read-onlyIdempotent

Usage-based billing; Default request estimate: $0.075 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
`offset`	No
`country`	No	Worldwide data only; values are case-insensitive.	ww
`category`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 15, 2026
- removedInput schema / properties / category / description
```
Removed value: -"Industry category, e.g. Finance."
```
- addedInput schema / properties / category / maxLength
```
Added value: +191
```
- addedInput schema / properties / category / minLength
```
Added value: +1
```
- 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 / 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 / offset / description
```
Removed value: -"Row offset for pagination."
```
- addedInput schema / properties / offset / maximum
```
Added value: +100000
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```
Changed11 schema fields changedOct 15, 2026
- addedInput schema / properties / category / description
```
Added value: +"Industry category, e.g. Finance."
```
- removedInput schema / properties / category / maxLength
```
Removed value: -191
```
- removedInput schema / properties / category / minLength
```
Removed value: -1
```
- 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 / 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 / offset / description
```
Added value: +"Row offset for pagination."
```
- removedInput schema / properties / offset / maximum
```
Removed value: -100000
```
- removedInput schema / properties / offset / minimum
```
Removed value: -0
```
Changed11 schema fields changedOct 15, 2026
- removedInput schema / properties / category / description
```
Removed value: -"Industry category, e.g. Finance."
```
- addedInput schema / properties / category / maxLength
```
Added value: +191
```
- addedInput schema / properties / category / minLength
```
Added value: +1
```
- 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 / 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 / offset / description
```
Removed value: -"Row offset for pagination."
```
- addedInput schema / properties / offset / maximum
```
Added value: +100000
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```
First observedSep 15, 2026

TDQS

D1.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description's only contribution is billing disclosure ($0.075 USD default estimate per similarweb_credit, usage-based, non-fixed), which is a genuine behavioral trait beyond the annotations, though it discloses nothing about the operation itself.

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 consists solely of an HTML-comment pricing block with no front-loaded statement of purpose. Being brief here reflects missing content rather than efficient concision.

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 4-parameter, paid, read-only ranking tool with an output schema (so return values need not be described), the description still omits purpose, parameter semantics, and usage context. It is inadequate for an agent to invoke the tool correctly.

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 coverage is only 25% across 4 parameters (category, limit, offset, country), and the description adds zero meaning for any of them. Required fields like category and limit are entirely unexplained, and the description does not compensate for the coverage gap.

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 boilerplate block, so an agent learns nothing about retrieving a SimilarWeb top-sites ranking, what a 'category' means, or how this differs from siblings like get_similarweb_ranking or list_categories.

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, and no prerequisites or exclusions. With 30+ siblings, the complete absence of routing guidance leaves the agent unable to choose this tool over any other.

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?