Skip to main content
Glama
Sign In

invisit

by dev.invisit
OverviewDiscussionsAdmin

Traffic over time

get_timeseries
Read-onlyIdempotent

Visits and pageviews per hour, day or week across a window, with any timeline annotations that fall inside it. Use it to find when something changed. With event_name, that custom event and its conversions per bucket instead.

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": {
      "site_id": "<site_id>"
    },
    "name": "get_timeseries"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day, inclusive, YYYY-MM-DD; default today
fromNoFirst day, YYYY-MM-DD; overrides period
periodNoWindow ending now; days are whole days in the timezone. Ignored when from is set.30d
filtersNoKeep only matching traffic; values of one dimension are OR-ed, dimensions AND-ed
site_idYessite_id from list_sites; a site name, slug or domain also resolves
intervalNoBucket size; default picks one that suits the window
timezoneNoIANA zone for day boundaries; default the user's
event_nameNoA custom event, as get_breakdown custom_events names it

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive behavior, so the bar is lower. The description adds real context beyond them: results include timeline annotations falling inside the window, and event_name switches the returned metrics to that event and its conversions rather than visits/pageviews — a behavioral fact not in the annotations or schema.

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

Conciseness5/5

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

Three short sentences, each carrying distinct information: what is returned, when to reach for it, and the alternate mode. Front-loaded with the resource and granularity; no filler or repetition of schema detail.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description takes responsibility for describing the return content (visits, pageviews, timeline annotations) and the event_name variant, and the 8 parameters are fully documented in the schema. Nothing essential for correct invocation is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. The description goes further by explaining the effect of event_name on output semantics (conversions per bucket rather than traffic), which the schema only describes as 'a custom event'. It does not add anything about filters, timezone, or from/to precedence, but those are already documented in the schema.

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?

States a specific resource and granularity ('visits and pageviews per hour, day or week across a window') plus a secondary mode ('with event_name, that custom event and its conversions per bucket instead'). An agent can distinguish this from get_breakdown or get_overview by the time-bucketed output, though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

'Use it to find when something changed' gives one clear usage context (trend/anomaly timing) and the event_name clause implies a second use case. However, there is no explicit when-not guidance and no routing to alternatives like get_breakdown for dimension comparisons, leaving the agent to infer boundaries.

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

All invisit 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