Skip to main content
Glama
Sign In

Convika

by com.convika
OverviewDiscussionsAdmin

Get analytics summary

get_analytics_summary
Read-onlyIdempotent

Check how a landing page is performing — pageviews, visitors, CTA clicks, referrers, and more.

Use when the user asks about traffic, performance, conversions, or how their page is doing. Returns daily breakdown, top pages, referrers, and country data.

  • Short-term periods: 7d (default), 30d, 90d

  • Long-term periods: 180d, 365d, all (Pro/MAX only) Visitors here are this page's; the dashboard's site overview counts people across a site, a different number. For deeper analysis (device breakdown, UTM, hourly data, period comparison), use get_analytics_detail instead. Dates and hours are in the workspace's time zone, UTC when the workspace has none set. Pass timeZone, an IANA name such as America/New_York, for days in another zone; it changes only this response, never the workspace's time zone. The result's timeZone field names the zone used, and timeZoneSource says where it came from (argument, workspace, or default). A row for today's date in that zone counts only the hours so far. When timeZonePending is set, the workspace is switching to that zone once its history is recomputed. 180d, 365d, and all come from daily summaries kept in the workspace's time zone, so a different timeZone isn't used there: the result stays in the summaries' zone and names the zone you passed as requestedTimeZone.

Input Schema

NameRequiredDescriptionDefault
periodNoTime period for the analytics summary. 180d/365d/all require Pro or MAX plan.7d
siteIdYesThe ID of the page to get analytics for
timeZoneNoIANA time zone name for the days in this response, such as America/New_York, Europe/Berlin, or Asia/Tokyo. Leave it out for the workspace's time zone (UTC when none is set). It affects only this response: the workspace's time zone stays as it is, and only the workspace's owner changes it, in the dashboard's Settings. Abbreviations such as EST and offsets such as +09:00 aren't accepted.
botFilterNoWhether to exclude known bots and vulnerability scanner traffic. Defaults to exclude. Use include only for diagnostics.exclude

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / siteId / description
      Previous value: -"The ID of the site to get analytics for"New value: +"The ID of the page to get analytics for"
  2. Changed1 schema field changed
    • addedInput schema / properties / timeZone
      Added value: +{
+  "description": "IANA time zone name for the days in this response, such as America/New_York, Europe/Berlin, or Asia/Tokyo. Leave it out for the workspace's time zone (UTC when none is set). It affects only this response: the workspace's time zone stays as it is, and only the workspace's owner changes it, in the dashboard's Settings. Abbreviations such as EST and offsets such as +09:00 aren't accepted.",
+  "maxLength": 64,
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / period / description
      Previous value: -"Time period for the analytics summary. 180d/365d/all require Pro or Max plan."New value: +"Time period for the analytics summary. 180d/365d/all require Pro or MAX plan."
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent safety, and the description goes far beyond them: plan gating for long periods, that timeZone only affects this response and never the workspace setting, that long periods ignore timeZone and report requestedTimeZone, that today's row is partial, and the timeZonePending state. These are non-obvious behavioral facts an agent could not infer from 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.

Conciseness4/5

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

Purpose and usage triggers are front-loaded ahead of the detail, which is the right order. The final timezone paragraph, however, is a dense multi-clause block covering five distinct behaviors that would read better as separate points, costing some scannability.

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?

There is no output schema, yet the description describes the return shape (daily breakdown, top pages, referrers, country) plus the timeZone/timeZoneSource/timeZonePending fields. For a 4-parameter, read-only analytics call, nothing material needed to call it correctly 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 coverage is 100%, so the baseline is 3, but the description adds semantics the schema does not: the interaction between long periods (180d/365d/all) and timeZone, and how the response signals which zone was actually used. botFilter is left entirely to the schema, which limits it to a 4.

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

Purpose5/5

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

The opening sentence names a specific verb+resource and enumerates the actual metrics returned (pageviews, visitors, CTA clicks, referrers). It also pre-empts confusion with get_analytics_detail by scoping 'deeper analysis' elsewhere, so an agent can distinguish it from siblings without opening a schema.

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

Usage Guidelines5/5

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

It gives an explicit trigger ('when the user asks about traffic, performance, conversions, or how their page is doing') and names the alternative for deeper analysis (get_analytics_detail with device/UTM/hourly/comparison). It also warns that its visitor count differs from the dashboard's site overview, a real selection hazard.

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

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