Skip to main content
Glama
Sign In

AIsa Similarweb

by one.aisa
OverviewDiscussionsAdmin

Landing Pages

get_similarweb_landing_pages
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
domainYes
offsetNo
countryNoWorldwide data only; values are case-insensitive.ww
end_dateYes
start_dateYes
web_sourceNo
granularityNo
traffic_sourceNo
main_domain_onlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed18 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 / domain / description
      Removed value: -"Target domain, e.g. example.com."
    • addedInput schema / properties / domain / maxLength
      Added value: +253
    • addedInput schema / properties / domain / minLength
      Added value: +1
    • 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 / 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 / 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."
    • removedInput schema / properties / traffic_source / description
      Removed value: -"Traffic-source filter."
    • removedInput schema / properties / web_source / description
      Removed value: -"Traffic source device split. Allowed: desktop, mobile_web, total."
    • changedInput schema / required
      Previous value: -[
-  "domain",
-  "start_date",
-  "end_date",
-  "limit"
-]New value: +[
+  "domain",
+  "end_date",
+  "limit",
+  "start_date"
+]
  2. Changed18 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 / domain / description
      Added value: +"Target domain, e.g. example.com."
    • removedInput schema / properties / domain / maxLength
      Removed value: -253
    • removedInput schema / properties / domain / minLength
      Removed value: -1
    • 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 / 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 / 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."
    • addedInput schema / properties / traffic_source / description
      Added value: +"Traffic-source filter."
    • addedInput schema / properties / web_source / description
      Added value: +"Traffic source device split. Allowed: desktop, mobile_web, total."
    • changedInput schema / required
      Previous value: -[
-  "domain",
-  "end_date",
-  "limit",
-  "start_date"
-]New value: +[
+  "domain",
+  "start_date",
+  "end_date",
+  "limit"
+]
  3. Changed18 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 / domain / description
      Removed value: -"Target domain, e.g. example.com."
    • addedInput schema / properties / domain / maxLength
      Added value: +253
    • addedInput schema / properties / domain / minLength
      Added value: +1
    • 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 / 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 / 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."
    • removedInput schema / properties / traffic_source / description
      Removed value: -"Traffic-source filter."
    • removedInput schema / properties / web_source / description
      Removed value: -"Traffic source device split. Allowed: desktop, mobile_web, total."
    • changedInput schema / required
      Previous value: -[
-  "domain",
-  "start_date",
-  "end_date",
-  "limit"
-]New value: +[
+  "domain",
+  "end_date",
+  "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=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered without the description. The only added behavioral information is the usage-based pricing estimate ($0.075 USD per similarweb_credit), which is genuinely useful context not present in annotations, but it says nothing about data scope, rate limits, or result semantics.

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 about billing rather than the tool's function. It is structurally compact yet fails the 'every sentence earns its place' test because no sentence helps an agent invoke the tool correctly.

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?

Although an output schema exists (so return values need not be explained), the description omits the tool's purpose, usage context, and parameter meaning for a 10-parameter tool with 4 required fields. For a complex, expensive, open-world query tool, this is completely inadequate.

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 10% across 10 parameters, so the description must compensate — and it does not. Parameters like domain, start_date/end_date formats, limit, offset, traffic_source, web_source, granularity and main_domain_only are left completely undocumented in both the schema and 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 auto-generated pricing boilerplate and never states what the tool does. Nothing in it indicates that the tool retrieves SimilarWeb landing page data, what a 'landing page' record contains, or how it differs from siblings like get_similarweb_keywords. An agent reading only the description would have no idea what this tool returns.

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 usage guidance of any kind — no when-to-use, no when-not-to-use, and no routing to the many sibling tools (get_similarweb_keywords, get_semrush_url_organic_keywords, etc.). The description gives the agent no basis for choosing this tool over alternatives.

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

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