Skip to main content
Glama

AIsa Go-To-Market

by one.aisa
OverviewDiscussionsAdmin

Website Traffic Snapshot

get_similarweb_website_traffic_snapshot
Read-onlyIdempotent

Usage-based billing; Default request estimate: $0.3 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
monthNoComplete month in YYYY-MM.
domainYesBare website hostname without scheme, path, port, or credentials.
countryNoWorldwide data only; values are case-insensitive.ww

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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 / month
      Added value: +{
+  "description": "Complete month in YYYY-MM.",
+  "type": "string",
+  "x-aisa-default-policy": "previous_complete_utc_month"
+}
  2. Changed4 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 / month
      Removed value: -{
-  "description": "Complete month in YYYY-MM.",
-  "type": "string",
-  "x-aisa-default-policy": "previous_complete_utc_month"
-}
  3. Changed4 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 / month
      Added value: +{
+  "description": "Complete month in YYYY-MM.",
+  "type": "string",
+  "x-aisa-default-policy": "previous_complete_utc_month"
+}
  4. First observed

TDQS

C2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description does add genuinely non-annotation behavior: usage-based billing with a stated unit rate and a default cost estimate, which is useful for cost-aware agents. It still omits any disclosure of response shape, latency, or credit consumption per call beyond the estimate.

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

Conciseness3/5

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

The text is short and front-loaded, but every sentence is pricing metadata rather than tool guidance, so the brevity reflects missing content rather than disciplined concision. Nothing is wasted, but nothing about the operation is conveyed either.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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, and annotations cover safety, but the description supplies no functional framing at all for a tool that competes with a dozen overlapping similarweb traffic tools. An agent cannot tell what a 'traffic snapshot' includes (visits, pageviews, bounce rate, duration) versus its siblings.

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%, and the schema documents domain, month (YYYY-MM, defaulting to previous complete UTC month) and country (worldwide only). The description adds no parameter meaning whatsoever, so the baseline 3 applies.

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 pricing boilerplate (usage-based billing, $0.3 estimate, $0.075 per credit) and says nothing about what the tool retrieves or returns. Only the tool name and title hint at 'website traffic snapshot', which is not sufficient to distinguish it from siblings like get_similarweb_traffic_engagement or get_similarweb_website_traffic_trend.

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 prerequisites, and no mention of alternatives. With 30+ similarweb siblings, the absence of any routing guidance leaves the agent unable to choose this tool over the many adjacent traffic metrics tools.

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