Skip to main content
Glama

AIsa Go-To-Market

by one.aisa
OverviewDiscussionsAdmin

Traffic & Engagement

get_similarweb_traffic_engagement
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
mtdNo
domainYes
countryNoWorldwide data only; values are case-insensitive.ww
metricsYes
end_dateYes
start_dateYes
web_sourceNo
granularityNomonthly
main_domain_onlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 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. Default: monthly."
    • removedInput schema / properties / main_domain_only / description
      Removed value: -"Restrict to the main domain only (true/false). Default: True."
    • removedInput schema / properties / metrics / description
      Removed value: -"Comma-separated metrics, e.g. visits,pages_per_visit."
    • addedInput schema / properties / metrics / x-aisa-delimiter
      Added value: +","
    • addedInput schema / properties / metrics / x-aisa-maxItems
      Added value: +8
    • addedInput schema / properties / metrics / x-aisa-minItems
      Added value: +1
    • removedInput schema / properties / mtd / description
      Removed value: -"Month-to-date flag (true/false)."
    • removedInput schema / properties / start_date / description
      Removed value: -"Start month, format YYYY-MM."
    • 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",
-  "metrics"
-]New value: +[
+  "domain",
+  "end_date",
+  "metrics",
+  "start_date"
+]
  2. Changed16 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. Default: monthly."
    • addedInput schema / properties / main_domain_only / description
      Added value: +"Restrict to the main domain only (true/false). Default: True."
    • addedInput schema / properties / metrics / description
      Added value: +"Comma-separated metrics, e.g. visits,pages_per_visit."
    • removedInput schema / properties / metrics / x-aisa-delimiter
      Removed value: -","
    • removedInput schema / properties / metrics / x-aisa-maxItems
      Removed value: -8
    • removedInput schema / properties / metrics / x-aisa-minItems
      Removed value: -1
    • addedInput schema / properties / mtd / description
      Added value: +"Month-to-date flag (true/false)."
    • addedInput schema / properties / start_date / description
      Added value: +"Start month, format YYYY-MM."
    • 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",
-  "metrics",
-  "start_date"
-]New value: +[
+  "domain",
+  "start_date",
+  "end_date",
+  "metrics"
+]
  3. Changed16 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. Default: monthly."
    • removedInput schema / properties / main_domain_only / description
      Removed value: -"Restrict to the main domain only (true/false). Default: True."
    • removedInput schema / properties / metrics / description
      Removed value: -"Comma-separated metrics, e.g. visits,pages_per_visit."
    • addedInput schema / properties / metrics / x-aisa-delimiter
      Added value: +","
    • addedInput schema / properties / metrics / x-aisa-maxItems
      Added value: +8
    • addedInput schema / properties / metrics / x-aisa-minItems
      Added value: +1
    • removedInput schema / properties / mtd / description
      Removed value: -"Month-to-date flag (true/false)."
    • removedInput schema / properties / start_date / description
      Removed value: -"Start month, format YYYY-MM."
    • 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",
-  "metrics"
-]New value: +[
+  "domain",
+  "end_date",
+  "metrics",
+  "start_date"
+]
  4. First observed

TDQS

D1.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so safety semantics are covered. The description does add genuinely useful non-annotation context: usage-based billing with a $0.075 USD per-request estimate and a similarweb_credit unit rate. However it says nothing about rate limits, auth, or what data is returned.

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 word is billing boilerplate that does not help an agent select or invoke the tool. Conciseness without relevance is under-specification, not efficiency.

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 9-parameter tool with only 11% schema coverage, an output schema, and a dense sibling set, the description omits purpose, usage, and all parameter semantics. Even granting that the output schema removes the need to explain return values, the definition is unusable for correct invocation.

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 11% across 9 parameters (4 required: domain, start_date, end_date, metrics), and the description contributes no parameter meaning at all — no mention of domains, date ranges, metric names, or the enum-constrained country/web_source/granularity values. This is the worst case for a high-parameter tool.

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 an auto-generated pricing notice and never states what the tool does. Neither the verb nor the resource is defined beyond what the tool name and title ('Traffic & Engagement') imply, and no sibling is distinguished.

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 prerequisites, and no mention of alternatives among the ~30 SimilarWeb siblings (e.g., website_traffic_snapshot, traffic_trend, marketing_channel_sources_legacy). An agent gets zero routing information.

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