Skip to main content
Glama
Sign In

AIsa Sales

by one.aisa
OverviewDiscussionsAdmin

SERP Players - Clicks over time

get_similarweb_serp_players_timeseries
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

NameRequiredDescriptionDefault
limitYes
offsetNo
countryNoWorldwide data only; values are case-insensitive.ww
end_dateYes
keywordsYes
start_dateYes
granularityNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • 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"
+]
  2. Changed14 schema fields changed
    • 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"
+]
  3. Changed14 schema fields changed
    • 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"
+]
  4. First observed

TDQS

D1.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description's only added value is cost transparency (~$0.075 per credit), which is genuinely useful context but says nothing about behavior, constraints, or effects. No contradiction with annotations.

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 off-topic boilerplate rather than tool documentation, so brevity here reflects absence of content, not efficient structure. The pricing note is front-loaded and clearly delimited, which is the only structural merit.

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?

With 7 parameters at 14% coverage, 4 required fields, no parameter documentation, and no purpose statement, the definition is unusable for correct invocation. The existence of an output schema excuses explaining return values but nothing else that is missing here.

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, so the description carries a heavy burden — and it communicates nothing about limit, offset, keywords, start_date, end_date, country, or granularity. Required date-range and keyword-delimited params are entirely unexplained.

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 aisa-pricing boilerplate about usage-based billing. An agent gets no verb, resource, or scope from the description body, and even the title's hint ('SERP Players - Clicks over time') is left unelaborated. This is effectively a missing description.

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, when-not-to-use, or alternative guidance of any kind. Nothing distinguishes this tool from sibling 'get_similarweb_serp_players_aggregated' or the many other get_similarweb_* tools, so the agent has no basis for 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 toolsInspect
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