Skip to main content
Glama
Sign In
VisiblyAI MCP Server

VisiblyAI MCP Server

by AntonioBlago
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_historical_traffic

Retrieve historical traffic trends for any domain over up to five years, segmented by location and date range.

Instructions

Get historical traffic trends (up to 5 years). Credits: varies.

Requires VISIBLYAI_API_KEY. Use get_account_info to check your balance.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "get_historical_traffic"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
date_toNo
locationNoGermany
date_fromNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description partially compensates by noting that credits vary and data is limited to 5 years. However, it lacks details on rate limits, pagination, or side effects. The cost variability is useful, but overall transparency is moderate.

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

Conciseness4/5

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

The description is concise, with the purpose stated in the first sentence and prerequisites in the second. It is front-loaded and contains no unnecessary information. However, it could be slightly more informative without losing conciseness.

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?

Given 4 parameters (1 required) and an existing output schema, the description omits important context such as required parameter (domain), default values for location and date_from/to, and expected output format. The tool is moderately complex, but the description leaves significant gaps.

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?

The description adds no parameter details beyond what the input schema provides. It does not explain the meaning of 'location', 'date_from', 'date_to', or the required 'domain'. With 0% schema coverage, the description fails to compensate, leaving the agent without guidance on how to use parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves historical traffic trends with a 5-year limit. The verb 'get' and resource 'historical traffic trends' are specific enough, and it implicitly distinguishes from sibling 'get_traffic_snapshot' by specifying historical data. However, it could more explicitly differentiate from other traffic-related tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'get_traffic_snapshot' or 'get_competitors'. The only usage advice is to check account balance via 'get_account_info', which is more about prerequisites than comparative use.

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

Deploy Server

Other Tools