Skip to main content
Glama
Sign In

Convika

by com.convika
OverviewDiscussionsAdmin

Get analytics for all pages

get_portfolio_analytics
Read-onlyIdempotent

Get a performance overview of ALL landing pages at once — pageviews, visitors, CTA clicks, and form submissions for every page.

Use when the user asks about overall performance, wants a summary of all pages, or says something like "how are my pages doing?" or "show me all LP performance". Returns a flat table-friendly summary with key metrics per page. No siteId needed — automatically fetches all pages. For detailed analytics on a specific page, use get_analytics_summary or get_analytics_detail instead. Periods: 7d (default), 30d, 90d. Long-term periods are not available for portfolio view. Visitors here add up each page, so one person on two pages counts twice; the dashboard's site overview counts people across a site, so its number can be lower. 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.

Input Schema

NameRequiredDescriptionDefault
periodNoTime period for the analytics summary.7d
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
    • 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"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, and the description adds genuinely new context beyond that: no siteId is required, results are aggregated per page with double-counted visitors relative to the dashboard's site overview, and the response is timezone-sensitive with timeZonePending indicating an in-progress zone switch. The aggregation caveat is exactly the kind of surprising behavior an agent would otherwise misinterpret.

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?

Well front-loaded: purpose, then usage triggers, then alternatives, then edge cases. The timezone paragraph largely restates the schema's timeZone description (IANA names, examples) and is the one section that could be trimmed, though it does add the timeZoneSource/timeZonePending return fields.

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 steps in to describe the return shape ('flat table-friendly summary with key metrics per page') and names the metadata fields the caller must interpret. Combined with the aggregation and timezone caveats, an agent has everything needed to call this correctly and read the result.

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 meaning beyond the schema for period (only 7d/30d/90d, long-term unavailable) and for timeZone (response-scoped, echoed back via timeZone/timeZoneSource, today's row is partial). It never mentions botFilter, so the schema carries that parameter alone.

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 ('Get a performance overview of ALL landing pages at once') and enumerates the metrics returned (pageviews, visitors, CTA clicks, form submissions). It explicitly distinguishes itself from the page-scoped siblings get_analytics_summary and get_analytics_detail, so an agent can pick it without opening any 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?

Gives concrete triggers ('overall performance', 'how are my pages doing?') and names the alternative tools plus the condition that selects them ('For detailed analytics on a specific page, use get_analytics_summary or get_analytics_detail instead'). It also states a negative constraint: long-term periods are unavailable for the portfolio view.

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