Skip to main content
Glama
Sign In

fivebar

by ar.fiveb
OverviewDiscussionsAdmin

Site summary

get_site_summary
Read-onlyIdempotent

A site's figures over a range beside the period before: pageviews, visits, visitors, bounce rate and visit duration, each one's change, the counts by day, week or month, and the top channels, sources, pages and countries. The answer's caveats are the rules that apply to its figures, such as visitors being visitor-days or today being partial: read them before reporting any figure, and pass on those that change what it means. Name the site by its domain, and the range one way: range, a preset; days, from 1 to 3660, with ending; or from and to, as YYYY-MM-DD. With none, it is the 7 whole days to yesterday. A range that cannot be read exactly as asked is refused, not moved, saying why and naming the site's today, and so is a filter, saying why. filters, at most 6 and one to a dimension, each narrows every figure. The answer echoes the site, range and filters with a dashboard link; then totals; previous, the period compared with and its totals; change, each figure's as a whole percentage of the previous, bounce rate's in points, null where there is none; per_day, where the periods differ in length; basis, how their days were counted; ended_visits; series; and top. Under a goal filter the figures are the goal's conversions, events and conversion rate. Under a source, referrer or campaign filter, other_values_containing lists stored values close to the filter's, such as Google News beside Google; where filters match nothing, suggestions offers values that do.

Input Schema

NameRequiredDescriptionDefault
toNoWith from: the last day, as YYYY-MM-DD, not after today.
daysNoThe last this many days, ending today unless ending says yesterday.
fromNoWith to: the first day, as YYYY-MM-DD.
rangeNoA preset: today; yesterday; this-week, Monday to today; last-7-days, today and the 6 days before it; last-week, Monday to Sunday of the week before this one; last-14-days, today and the 13 days before it; this-month, the 1st of this month to today; last-30-days, today and the 29 days before it; last-month, the whole of the month before this one; all-time, the day the site was added to today. The -fri, -sat and -sun weeks start on Friday, Saturday or Sunday. One running to today includes today so far; for whole days, use days with ending yesterday.
domainYesA domain from list_sites, or any public site's.
endingNoWith days: the last day, today by default.
filtersNoEach narrows every figure to what has exactly that value, case and all, so google is not Google; all must hold.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / range / description
      Previous value: -"A preset: today; yesterday; this-week, Monday to today; this-week-sun, Sunday to today; last-7-days, today and the 6 days before it; last-week, Monday to Sunday of the week before this one; last-week-sun, Sunday to Saturday of the week before this one; last-14-days, today and the 13 days before it; this-month, the 1st of this month to today; last-30-days, today and the 29 days before it; last-month, the whole of the month before this one; all-time, the day the site was added to today. One running to today includes today so far; for whole days, use days with ending yesterday."New value: +"A preset: today; yesterday; this-week, Monday to today; last-7-days, today and the 6 days before it; last-week, Monday to Sunday of the week before this one; last-14-days, today and the 13 days before it; this-month, the 1st of this month to today; last-30-days, today and the 29 days before it; last-month, the whole of the month before this one; all-time, the day the site was added to today. The -fri, -sat and -sun weeks start on Friday, Saturday or Sunday. One running to today includes today so far; for whole days, use days with ending yesterday."
    • changedInput schema / properties / range / enum
      Previous value: -[
-  "today",
-  "yesterday",
-  "this-week",
-  "this-week-sun",
-  "last-7-days",
-  "last-week",
-  "last-week-sun",
-  "last-14-days",
-  "this-month",
-  "last-30-days",
-  "last-month",
-  "all-time"
-]New value: +[
+  "today",
+  "yesterday",
+  "this-week",
+  "this-week-fri",
+  "this-week-sat",
+  "this-week-sun",
+  "last-7-days",
+  "last-week",
+  "last-week-fri",
+  "last-week-sat",
+  "last-week-sun",
+  "last-14-days",
+  "this-month",
+  "last-30-days",
+  "last-month",
+  "all-time"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / filters / items / properties / dimension / description
      Previous value: -"path: a page, as a path starting with /. entry and exit: the page a visit started or ended on, as a path. channel: where a visit came from by kind, as GA4 names them, such as Organic Search (AI Assistants is fivebar's own); get_site_breakdown by channel lists them. source: where a visit came from, by name, such as Google (Google search on any of its domains, and its app), Bing or Direct, or the utm_source, ref or source tag its link carried, with the names fivebar knows in its own spelling; there is no utm_source dimension. referrer: the host a visit came from, without www., such as google.com or google.co.uk. country: an ISO 3166 code in capitals, such as GB, not UK. city: a name, such as London. asn: the network a visit came through, by its AS number alone, such as 2856. device: Desktop, Mobile or Tablet. browser and os: names, such as Chrome, Safari, iOS or Windows. utm_medium, utm_campaign, utm_content and utm_term: the link's tags, as sent. goal: an event by its name as sent, such as Signup, or a page goal by its pattern, such as /thanks/*, as list_goals gives them. property: a custom property, named by property, such as plan, with its value as sent, such as pro; get_site_breakdown by property lists them. Each property is a dimension of its own."New value: +"path: a page, as a path starting with /. entry and exit: the page a visit started or ended on, as a path. channel: where a visit came from by kind, as GA4 names them, such as Organic Search, but for AI Assistants, which GA4 calls AI Assistant; get_site_breakdown by channel lists them. source: where a visit came from, by name, such as Google (Google search on any of its domains, and its app), Bing or Direct, or the utm_source, ref or source tag its link carried, with the names fivebar knows in its own spelling; there is no utm_source dimension. referrer: the host a visit came from, without www., such as google.com or google.co.uk. country: an ISO 3166 code in capitals, such as GB, not UK. city: a name, such as London. asn: the network a visit came through, by its AS number alone, such as 2856. device: Desktop, Mobile or Tablet. browser and os: names, such as Chrome, Safari, iOS or Windows. utm_medium, utm_campaign, utm_content and utm_term: the link's tags, as sent. goal: an event by its name as sent, such as Signup, or a page goal by its pattern, such as /thanks/*, as list_goals gives them. property: a custom property, named by property, such as plan, with its value as sent, such as pro; get_site_breakdown by property lists them. Each property is a dimension of its own."
  3. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description still adds substantial behavior beyond that: invalid ranges are refused rather than silently moved, the refusal names the site's 'today'; filters that match nothing return suggestions and other_values_containing. It also enumerates the full response surface (totals, previous, change as whole percentage with bounce rate in points and null when undefined, per_day only when periods differ in length, basis, ended_visits, series, top, dashboard link), which matters because there is no output schema.

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?

The purpose is front-loaded correctly and no sentence is pure filler, but the body is a single dense ~300-word paragraph that mixes response shape, range semantics, refusal behavior, filter rules and fallback behavior with no visual separation. For a definition of this complexity, headers or short paragraphs would materially improve scannability without losing content.

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 7 parameters, three mutually exclusive range forms, nested filter objects, no output schema and rich refusals, this description covers what an agent needs: how to specify the range, what the default is, what happens on invalid input, how filters narrow and what happens when they match nothing, and the full shape of the returned object including caveats. Nothing material is left to guess.

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 schema baseline of 3 already applies, and the description still adds meaning: it makes the three range forms mutually exclusive ('the range one way: range... days... or from and to'), states the default when none is given, and constrains filters to at most 6 with one per dimension — a constraint not stated in the schema. It also explains that under a goal filter the figures become conversions/events/conversion rate, which the schema does not say. It loses the extra point only because some of its length restates schema enum text.

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?

The opening sentence names the resource (a site's figures) and enumerates concretely what is returned: pageviews, visits, visitors, bounce rate, visit duration, with their change, per-day/week/month counts, and top channels/sources/pages/countries. That is far more specific than a generic 'gets site data'. It stops short of 5 because it never positions itself against the closest siblings (get_overview, get_site_engagement, get_site_breakdown); it references get_site_breakdown only inside a filter definition, not as routing guidance.

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?

There is real usage guidance, but it is about how to supply arguments (name the site by domain; pick one of three mutually exclusive range forms; default of 7 whole days to yesterday) rather than when this tool is the right choice. The instruction to read the caveats and pass them on is useful operational guidance. There is no statement of when to prefer get_overview or get_site_breakdown instead, so the when-to-use-vs-alternatives bar is not met.

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

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