Skip to main content
Glama
Sign In

DevDome Analytics

by com.devdome
OverviewDiscussionsAdmin

Get Daily Traffic

get_timeseries
Read-only

Daily traffic series for a site (visits, visitors, pageviews, clicks, bots per day, in the site's timezone). Window by days, or from and to (YYYY-MM-DD); omit both for the full history the plan retains.

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

Input Schema

NameRequiredDescriptionDefault
toNoWindow end, YYYY-MM-DD (inclusive)
daysNo
fromNoWindow start, YYYY-MM-DD
siteYes
filtersNoNarrow the report to the visits that match ALL of these (the dashboard's click-to-filter), inside the same window as the report. Omit for everything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / filters
      Added value: +{
+  "additionalProperties": false,
+  "description": "Narrow the report to the visits that match ALL of these (the dashboard's click-to-filter), inside the same window as the report. Omit for everything.",
+  "properties": {
+    "browser": {
+      "description": "Browser name as get_breakdown dimension=browsers lists it",
+      "type": "string"
+    },
+    "campaign": {
+      "description": "utm source|medium|campaign exactly as a get_breakdown dimension=campaigns row; an empty part matches any, e.g. newsletter||",
+      "type": "string"
+    },
+    "country": {
+      "description": "ISO 3166-1 alpha-2 code, e.g. US; several joined with |, e.g. US|DE",
+      "type": "string"
+    },
+    "device": {
+      "description": "Device class as get_breakdown dimension=devices lists it (desktop, mobile, tablet)",
+      "type": "string"
+    },
+    "event": {
+      "description": "Visits that fired this custom event name (get_events lists the names)",
+      "type": "string"
+    },
+    "goal": {
+      "description": "Visits that completed this saved goal, by the id get_goals returns",
+      "type": "string"
+    },
+    "os": {
+      "description": "Operating system as get_breakdown dimension=os lists it",
+      "type": "string"
+    },
+    "page": {
+      "description": "Visits that viewed this page path, e.g. /pricing",
+      "type": "string"
+    },
+    "referrer": {
+      "description": "Visits that arrived from this referrer host, e.g. google.com",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / from / description
      Previous value: -"Accepted, not applied: use days"New value: +"Window start, YYYY-MM-DD"
    • changedInput schema / properties / to / description
      Previous value: -"Accepted, not applied: use days"New value: +"Window end, YYYY-MM-DD (inclusive)"
  3. Changed2 schema fields changed
    • addedInput schema / properties / from / description
      Added value: +"Accepted, not applied: use days"
    • addedInput schema / properties / to / description
      Added value: +"Accepted, not applied: use days"
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, so the safety profile is covered. The description adds valuable behavior beyond that: results are in the site's timezone, and omitting the window returns 'the full history the plan retains' — a potentially large default response an agent should know about. No pagination or rate-limit info, but that is a minor gap given annotation coverage.

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?

Two sentences, front-loaded with purpose before windowing details. The parenthetical metric list is dense but every element carries information; nothing is redundant.

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

Completeness4/5

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

No output schema exists, but the description effectively enumerates the returned series (metrics per day) and the timezone. Windowing and full-history defaults are covered; the only missing piece is any hint about response size or pagination for the unbounded full-history case, which matters but is not critical for a read-only reporting call.

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 coverage is 60%, and the description fills the most important hole: the undocumented 'days' parameter gets semantics ('Window by days'), as does the interaction with from/to and the default full-history behavior when both are omitted. The nested filters object is left entirely to the schema, which documents it richly, so this is a reasonable balance.

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 concrete verb and resource ('Daily traffic series for a site') and lists the exact metrics returned (visits, visitors, pageviews, clicks, bots per day) plus timezone semantics. It does not name or differentiate from siblings like get_hourly or get_stats, so an agent must infer the daily-vs-hourly distinction from the word 'Daily' alone.

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?

The description explains windowing options ('days, or from and to') and the omit-both fallback, which is usage guidance for parameters. It never says when to choose this tool over get_hourly, get_stats, or get_breakdown, so alternative selection is implied only by the word 'Daily'.

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

All DevDome Analytics 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