AIsa Sales

Website Technologies

get_similarweb_technologies

Read-onlyIdempotent

Usage-based billing; Default request estimate: $0.75 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.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful cost behavior (default request estimate $0.75, $0.075 per similarweb_credit, account-specific pricing) but does not disclose other behavioral traits such as data freshness, rate limits, or authentication requirements.

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 front-loads pricing rather than purpose, and the entire description is off-topic for tool selection. The structure is not appropriate for a tool definition because no functional content is present.

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 tool with 9 parameters (5 required), 11% schema coverage, and an output schema, the description is completely inadequate. It omits purpose, usage guidance, and parameter semantics; the only context provided is billing metadata.

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 11% across 9 parameters, and the description contains zero parameter information. It does not explain domain, date ranges, granularity, limit, or any other input, so it completely fails to compensate for the sparse schema.

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 billing estimate and unit rate. The name and title suggest 'website technologies', but the description itself provides no functional verb, resource, or scope, so an agent cannot determine the tool's purpose from the text.

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 guidance is given on when to use this tool versus siblings such as get_similarweb_website_analysi_7399a9, get_similarweb_technology_* variants, or get_details. The only content is pricing, which does not help tool 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?