Skip to main content
Glama

AIsa Go-To-Market

by one.aisa
OverviewDiscussionsAdmin

Website Traffic Trend

get_similarweb_website_traffic_trend
Read-onlyIdempotent

Usage-based billing; Default request estimate: $0.45 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
domainYesBare website hostname without scheme, path, port, or credentials.
countryNoWorldwide data only; values are case-insensitive.ww
metricsNoOne to four supported Traffic & Engagement metrics.visits
end_dateNoInclusive last complete UTC month in YYYY-MM.
start_dateNoInclusive first month in YYYY-MM; provide together with end_date.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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"
+]
    • changedInput schema / properties / domain / description
      Previous value: -"Target domain, e.g. example.com."New value: +"Bare website hostname without scheme, path, port, or credentials."
    • addedInput schema / properties / end_date
      Added value: +{
+  "description": "Inclusive last complete UTC month in YYYY-MM.",
+  "type": "string"
+}
    • addedInput schema / properties / metrics
      Added value: +{
+  "default": "visits",
+  "description": "One to four supported Traffic & Engagement metrics.",
+  "type": "string",
+  "x-aisa-delimiter": ",",
+  "x-aisa-item-enum": [
+    "average_visit_duration",
+    "bounce_rate",
+    "new_users",
+    "page_views",
+    "pages_per_visit",
+    "returning_users",
+    "unique_visitors",
+    "visits"
+  ],
+  "x-aisa-maxItems": 4
+}
    • addedInput schema / properties / start_date
      Added value: +{
+  "description": "Inclusive first month in YYYY-MM; provide together with end_date.",
+  "type": "string"
+}
  2. Changed6 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"
+]
    • changedInput schema / properties / domain / description
      Previous value: -"Bare website hostname without scheme, path, port, or credentials."New value: +"Target domain, e.g. example.com."
    • removedInput schema / properties / end_date
      Removed value: -{
-  "description": "Inclusive last complete UTC month in YYYY-MM.",
-  "type": "string"
-}
    • removedInput schema / properties / metrics
      Removed value: -{
-  "default": "visits",
-  "description": "One to four supported Traffic & Engagement metrics.",
-  "type": "string",
-  "x-aisa-delimiter": ",",
-  "x-aisa-item-enum": [
-    "average_visit_duration",
-    "bounce_rate",
-    "new_users",
-    "page_views",
-    "pages_per_visit",
-    "returning_users",
-    "unique_visitors",
-    "visits"
-  ],
-  "x-aisa-maxItems": 4
-}
    • removedInput schema / properties / start_date
      Removed value: -{
-  "description": "Inclusive first month in YYYY-MM; provide together with end_date.",
-  "type": "string"
-}
  3. Changed6 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"
+]
    • changedInput schema / properties / domain / description
      Previous value: -"Target domain, e.g. example.com."New value: +"Bare website hostname without scheme, path, port, or credentials."
    • addedInput schema / properties / end_date
      Added value: +{
+  "description": "Inclusive last complete UTC month in YYYY-MM.",
+  "type": "string"
+}
    • addedInput schema / properties / metrics
      Added value: +{
+  "default": "visits",
+  "description": "One to four supported Traffic & Engagement metrics.",
+  "type": "string",
+  "x-aisa-delimiter": ",",
+  "x-aisa-item-enum": [
+    "average_visit_duration",
+    "bounce_rate",
+    "new_users",
+    "page_views",
+    "pages_per_visit",
+    "returning_users",
+    "unique_visitors",
+    "visits"
+  ],
+  "x-aisa-maxItems": 4
+}
    • addedInput schema / properties / start_date
      Added value: +{
+  "description": "Inclusive first month in YYYY-MM; provide together with end_date.",
+  "type": "string"
+}
  4. First observed

TDQS

D1.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is covered. The description does add genuinely useful behavior beyond annotations: usage-based billing, a $0.45 default request estimate, and a $0.075 per similarweb_credit unit rate, which an agent should weigh before calling. However it discloses nothing about latency, time-window semantics, or result shape, so it is only partial.

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 and contains no padding, but every sentence is pricing boilerplate wrapped in HTML comment markers rather than task description. It is concise in size yet misdirected in content, and there is no front-loaded statement of purpose to anchor the rest.

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?

An output schema exists, so return values need not be explained, but the description still omits the trend/time-series semantics, default date behavior, and differentiation from the snapshot and traffic-engagement siblings. For a 5-parameter tool with three closely named siblings, this leaves the agent without the information needed to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents domain format, the country enum, the four-item metrics list, and the YYYY-MM date semantics; baseline 3 applies. The description adds no parameter meaning whatsoever beyond what the schema provides.

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; it is entirely a pricing banner. Only the tool name hints at retrieving a website traffic trend, and the description does nothing to confirm scope, distinguish trend from snapshot, or identify the resource beyond what the name already says.

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 exclusions, and no reference to alternatives such as get_similarweb_website_traffic_snapshot or get_similarweb_traffic_engagement, which are the most likely competing tools. An agent has no basis for choosing this tool over those siblings.

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

All AIsa Go-To-Market 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