AIsa Similarweb

SERP Players - Aggregated

get_similarweb_serp_players_aggregated

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
`end_date`	Yes
`keywords`	Yes
`start_date`	Yes
`granularity`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 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 / end_date / description
```
Removed value: -"End month, format YYYY-MM."
```
removedInput schema / properties / granularity / description
```
Removed value: -"Time granularity. Allowed: monthly."
```

removedInput schema / properties / keyword

Removed value: -{
-  "description": "Target keyword.",
-  "type": "string"
-}

addedInput schema / properties / keywords

Added value: +{
+  "type": "string",
+  "x-aisa-delimiter": ",",
+  "x-aisa-maxItems": 1,
+  "x-aisa-minItems": 1
+}

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
```
removedInput schema / properties / start_date / description
```
Removed value: -"Start month, format YYYY-MM."
```

changedInput schema / required

Previous value: -[
-  "keyword",
-  "start_date",
-  "end_date",
-  "limit"
-]New value: +[
+  "end_date",
+  "keywords",
+  "limit",
+  "start_date"
+]

Changed14 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 / end_date / description
```
Added value: +"End month, format YYYY-MM."
```
addedInput schema / properties / granularity / description
```
Added value: +"Time granularity. Allowed: monthly."
```

addedInput schema / properties / keyword

Added value: +{
+  "description": "Target keyword.",
+  "type": "string"
+}

removedInput schema / properties / keywords

Removed value: -{
-  "type": "string",
-  "x-aisa-delimiter": ",",
-  "x-aisa-maxItems": 1,
-  "x-aisa-minItems": 1
-}

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
```
addedInput schema / properties / start_date / description
```
Added value: +"Start month, format YYYY-MM."
```

changedInput schema / required

Previous value: -[
-  "end_date",
-  "keywords",
-  "limit",
-  "start_date"
-]New value: +[
+  "keyword",
+  "start_date",
+  "end_date",
+  "limit"
+]

Changed14 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 / end_date / description
```
Removed value: -"End month, format YYYY-MM."
```
removedInput schema / properties / granularity / description
```
Removed value: -"Time granularity. Allowed: monthly."
```

removedInput schema / properties / keyword

Removed value: -{
-  "description": "Target keyword.",
-  "type": "string"
-}

addedInput schema / properties / keywords

Added value: +{
+  "type": "string",
+  "x-aisa-delimiter": ",",
+  "x-aisa-maxItems": 1,
+  "x-aisa-minItems": 1
+}

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
```
removedInput schema / properties / start_date / description
```
Removed value: -"Start month, format YYYY-MM."
```

changedInput schema / required

Previous value: -[
-  "keyword",
-  "start_date",
-  "end_date",
-  "limit"
-]New value: +[
+  "end_date",
+  "keywords",
+  "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=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description's only added content is a usage-based price estimate ($0.075), which is genuinely useful operational context but says nothing about aggregation behavior, supported keyword counts, or data scope. Slight credit above the minimum.

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 every sentence is billing metadata unrelated to tool selection or invocation, wrapped in HTML comment tags that further bury it. There is no functional content to front-load — the space is misused rather than simply verbose.

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 7-parameter, 4-required analytics tool with 14% schema coverage, the description supplies none of the missing piece: what data is returned in aggregate form, what date range/keyword constraints mean, or how it relates to the timeseries sibling. An output schema exists so return format needn't be explained, but the input and purpose gaps leave the definition unusable on its own.

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 14% across 7 parameters (limit, offset, start_date, end_date, keywords, granularity, country), and the description provides no parameter semantics whatsoever — no date format, no keyword-delimiter behavior, no limit/offset meaning. The description fully fails to 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 contains no statement of what the tool does — only billing boilerplate. The title 'SERP Players - Aggregated' is the sole hint at purpose (aggregated SERP competitor data), and that comes from the title field, not the description, so an agent gets no functional explanation of this tool.

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 guidance, no conditions, and no reference to any of the ~30 siblings such as get_similarweb_serp_players_timeseries, which is the obvious alternative this tool needs to be distinguished from. The agent must guess entirely.

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

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