AIsa Sales

Website Keywords

get_similarweb_keywords

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
`domain`	Yes
`format`	No
`country`	No	Worldwide data only; values are case-insensitive.	ww
`end_date`	Yes
`start_date`	Yes
`web_source`	No
`granularity`	Yes
`main_domain_only`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 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: +2048
```
addedInput schema / properties / domain / minLength
```
Added value: +1
```
removedInput schema / properties / end_date / description
```
Removed value: -"End month, format YYYY-MM."
```
removedInput schema / properties / format / description
```
Removed value: -"Response format. Allowed: json."
```
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 / start_date / description
```
Removed value: -"Start month, format YYYY-MM."
```

removedInput schema / properties / web_source / description

Removed value: -"Traffic source device split. Allowed: total."

changedInput schema / required

Previous value: -[
-  "domain",
-  "start_date",
-  "end_date",
-  "granularity",
-  "limit"
-]New value: +[
+  "domain",
+  "end_date",
+  "granularity",
+  "limit",
+  "start_date"
+]

Changed15 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: -2048
```
removedInput schema / properties / domain / minLength
```
Removed value: -1
```
addedInput schema / properties / end_date / description
```
Added value: +"End month, format YYYY-MM."
```
addedInput schema / properties / format / description
```
Added value: +"Response format. Allowed: json."
```
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 / start_date / description
```
Added value: +"Start month, format YYYY-MM."
```

addedInput schema / properties / web_source / description

Added value: +"Traffic source device split. Allowed: total."

changedInput schema / required

Previous value: -[
-  "domain",
-  "end_date",
-  "granularity",
-  "limit",
-  "start_date"
-]New value: +[
+  "domain",
+  "start_date",
+  "end_date",
+  "granularity",
+  "limit"
+]

Changed15 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: +2048
```
addedInput schema / properties / domain / minLength
```
Added value: +1
```
removedInput schema / properties / end_date / description
```
Removed value: -"End month, format YYYY-MM."
```
removedInput schema / properties / format / description
```
Removed value: -"Response format. Allowed: json."
```
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 / start_date / description
```
Removed value: -"Start month, format YYYY-MM."
```

removedInput schema / properties / web_source / description

Removed value: -"Traffic source device split. Allowed: total."

changedInput schema / required

Previous value: -[
-  "domain",
-  "start_date",
-  "end_date",
-  "granularity",
-  "limit"
-]New value: +[
+  "domain",
+  "end_date",
+  "granularity",
+  "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 cover the operational profile (readOnly, idempotent, openWorld, non-destructive). The description's only additive behavioral content is the billing model — usage-based, ~$0.075 per similarweb_credit — which is genuinely useful cost context. However, it discloses nothing about data freshness, result size, or what the returned keyword records contain.

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 the brevity is under-specification rather than efficiency: the entire body is boilerplate pricing with zero functional content. The one useful sentence (per-credit rate) is buried in a compliance block rather than front-loaded as tool guidance.

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 9-parameter, 5-required tool with 11% schema coverage and a crowded sibling namespace, the description supplies no purpose, no usage routing, and no parameter semantics — it is functionally empty.

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 11% (only 'country' is documented), and there are 9 parameters including five required ones (domain, start_date, end_date, granularity, limit). The description explains none of them — no date format, no domain input convention, no meaning for granularity or web_source — leaving the agent to guess.

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 notice. An agent must infer from the name and title alone that this retrieves SimilarWeb keyword data, and it cannot distinguish this from the many get_semrush_* and get_dataforseo_keywords_* siblings.

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?

No when-to-use, when-not-to-use, or alternative guidance is given. The pricing block states cost but not the conditions under which this tool should be chosen over the adjacent get_similarweb_landing_pages or the Semrush/DataForSEO keyword tools.

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?