AIsa Sales

Audience Overlap

get_similarweb_audience_overlap

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

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 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 / domains / description

Removed value: -"Two to five target domains, comma-separated (e.g. cnn.com,bbc.com)."

addedInput schema / properties / domains / x-aisa-delimiter
```
Added value: +","
```
addedInput schema / properties / domains / x-aisa-maxItems
```
Added value: +5
```
addedInput schema / properties / domains / x-aisa-minItems
```
Added value: +2
```
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 / start_date / description
```
Removed value: -"Start month, format YYYY-MM."
```

changedInput schema / required

Previous value: -[
-  "domains",
-  "start_date",
-  "end_date"
-]New value: +[
+  "domains",
+  "end_date",
+  "start_date"
+]

Changed10 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 / domains / description

Added value: +"Two to five target domains, comma-separated (e.g. cnn.com,bbc.com)."

removedInput schema / properties / domains / x-aisa-delimiter
```
Removed value: -","
```
removedInput schema / properties / domains / x-aisa-maxItems
```
Removed value: -5
```
removedInput schema / properties / domains / x-aisa-minItems
```
Removed value: -2
```
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 / start_date / description
```
Added value: +"Start month, format YYYY-MM."
```

changedInput schema / required

Previous value: -[
-  "domains",
-  "end_date",
-  "start_date"
-]New value: +[
+  "domains",
+  "start_date",
+  "end_date"
+]

Changed10 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 / domains / description

Removed value: -"Two to five target domains, comma-separated (e.g. cnn.com,bbc.com)."

addedInput schema / properties / domains / x-aisa-delimiter
```
Added value: +","
```
addedInput schema / properties / domains / x-aisa-maxItems
```
Added value: +5
```
addedInput schema / properties / domains / x-aisa-minItems
```
Added value: +2
```
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 / start_date / description
```
Removed value: -"Start month, format YYYY-MM."
```

changedInput schema / required

Previous value: -[
-  "domains",
-  "start_date",
-  "end_date"
-]New value: +[
+  "domains",
+  "end_date",
+  "start_date"
+]

First observedSep 15, 2026

TDQS

D1.2/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 safety behavior is covered. The pricing block legitimately adds cost context (~$0.75 per default request, $0.075/credit), which is useful, but it discloses nothing about the operation itself or its output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is short but consists of HTML-comment boilerplate that is irrelevant to tool selection. It is not front-loaded with a purpose statement, so its brevity reflects under-specification rather than conciseness.

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 five-parameter data-retrieval tool with 3 required inputs and only 20% schema coverage, the description omits everything an agent needs to call it correctly. The existence of an output schema excuses return-value documentation but does not excuse the complete absence of functional context.

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 20%, so the description is obligated to compensate for undocumented parameters, yet it says nothing about domains (2-5, comma-delimited), date ranges, country, or granularity. The single documented parameter (country) is covered by the schema, not the description.

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 only a pricing disclaimer block and never states what the tool does. Nothing distinguishes audience overlap from siblings such as get_similarweb_deduplicated_audience or get_similarweb_audience_interest.

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 prerequisites, and no mention of alternatives. An agent must infer the tool's purpose entirely from the name.

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?