Skip to main content
Glama
Sign In

Convika

by com.convika
OverviewDiscussionsAdmin

Get analytics breakdown

get_analytics_detail
Read-onlyIdempotent

Deep-dive analytics with period comparison, device breakdown, UTM tracking, and CTA click analysis.

Use when the user wants to optimize campaigns, evaluate traffic sources, or understand user behavior in detail. Includes everything from get_analytics_summary PLUS:

  • CTA click breakdown (which buttons get clicked most)

  • Device breakdown (mobile/desktop/tablet)

  • UTM parameter analysis (source, medium, campaign)

  • Period-over-period comparison with change percentages

  • Hourly breakdown (short-term only) Periods: 7d (default), 30d, 90d | 180d, 365d, all (Pro/MAX only) With 90d, a timeZone other than the workspace's leaves the change figures null, except for form submissions: the previous 90 days come only from daily summaries kept in the workspace's time zone. Leave timeZone out for 90d changes. 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 detail. 180d/365d/all require Pro or MAX plan.7d
siteIdYesThe ID of the page to get detailed 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 detailed analytics for"New value: +"The ID of the page to get detailed 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 detail. 180d/365d/all require Pro or Max plan."New value: +"Time period for the analytics detail. 180d/365d/all require Pro or MAX plan."
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds substantially more: 90d changes go null when a non-workspace timeZone is passed, long periods come from daily summaries in the workspace's time zone, requestedTimeZone is reported instead of applied, timeZonePending signals a pending zone switch, and today's row is partial. These are non-obvious edge cases an agent could not infer from annotations.

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

Conciseness3/5

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

Well front-loaded with purpose and use case, but the multi-sentence time-zone block is dense and partly restates the schema's own timeZone description, including dashboard/settings commentary that an agent doesn't need. It's informative but not tight.

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?

For a 4-param read tool with no output schema, the description covers plan gating, period semantics, time-zone behavior, and several result field names, which is close to sufficient. It never sketches the overall response shape (what the breakdown rows contain), leaving a modest gap given there is no output schema to lean on.

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 baseline is 3, but the description adds real semantics beyond it: it explains why timeZone must be omitted for 90d change figures, that timeZone only affects this response and never the workspace setting, and how the result names the zone used (timeZone, timeZoneSource, requestedTimeZone). botFilter is left entirely to the schema, so it isn't a full 5.

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?

States a specific verb and resource (analytics detail/breakdown) and enumerates the concrete dimensions it returns: period comparison, device, UTM, CTA clicks, hourly. It explicitly positions itself against the sibling get_analytics_summary ('Includes everything from get_analytics_summary PLUS'), so an agent can separate the two without opening schemas.

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

Usage Guidelines4/5

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

Gives concrete use cases ('optimize campaigns, evaluate traffic sources, understand user behavior in detail') and implicitly routes simpler needs to get_analytics_summary via the 'PLUS' framing. It also warns that 180d/365d/all are Pro/MAX only. It stops short of an explicit 'use summary instead when...' exclusion, so it stops at a strong 4.

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