Skip to main content
Glama
Sign In

fivebar

by ar.fiveb
OverviewDiscussionsAdmin

Site bots

get_site_bots
Read-onlyIdempotent

The pageviews fivebar took for bots on a site over a range, beside the period before, as its Bots page has them: no other tool's figures count them. The answer's caveats are the rules that apply to its figures, such as only bots that run the site's script being counted: read them before reporting any figure, and pass on those that change what it means. Name the site and range as for get_site_summary, which refuses the same things. filters take only path, source, country, asn, browser and os; reason narrows to one reason they were taken for bots, and bot to one known bot. Bots are counted in pageviews alone. The answer echoes the site, range, filters, reason and bot, first_day being the first day a bot was kept for it, with a link to the Bots page; then totals, previous, change, per_day and basis, as get_site_summary's; share, their part of every pageview in the range, bots' and people's, a fraction of 1, with people's counted from counted_from where the range starts earlier; series, by the hour for a range of a day or two, else by day, week or month; and top, at most eight each of the reasons, bots, pages, sources, networks, countries, browsers and operating systems, each with its pageviews and the value reason or bot takes, or the filter to it.

Input Schema

NameRequiredDescriptionDefault
toNoWith from: the last day, as YYYY-MM-DD, not after today.
botNoOnly those of this known bot, as top.bots gives each, such as google or openai.
daysNoThe last this many days, ending today unless ending says yesterday.
fromNoWith to: the first day, as YYYY-MM-DD.
rangeNoA preset, as get_site_summary's range says what each covers.
domainYesA domain from list_sites, or any public site's.
endingNoWith days: the last day, today by default.
reasonNoOnly the pageviews taken for bots for this reason, as top.reasons gives each.
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. Changed1 schema field changed
    • 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. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive operation. The description adds meaningful behavioral context beyond annotations: only bots that run the site's script are counted, results are counted in pageviews alone, and caveats must be read and passed on when they change the meaning of a figure.

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 and the detail is relevant to a complex tool with no output schema, but the single dense paragraph is long, clause-heavy, and difficult to parse. It is appropriately information-rich yet not as concise or cleanly structured as it could be.

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 and nine parameters, the description carries the burden of explaining return values, and it does so thoroughly: echoed site/range/filters, totals, previous, change, per_day, basis, share with counted_from caveat, series granularity, and top breakdowns capped at eight. It also covers caveats and validation constraints.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all nine parameters, including enums and filter dimensions. The description reinforces some meanings (filters limit dimensions, reason and bot narrow to one value) and adds the get_site_summary cross-reference, but it does not substantially extend parameter semantics beyond the structured schema.

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 description states a specific resource and scope: bot pageviews for a site over a range, compared with the prior period, as shown on its Bots page. It explicitly distinguishes itself from other tools by saying 'no other tool's figures count them' and ties its site/range handling to get_site_summary.

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?

It gives clear context for use: read and pass on caveats before reporting figures, take filters only from the specified dimensions, and use get_site_summary's range conventions. It does not explicitly name a non-bot alternative (e.g., 'use get_site_summary for human pageviews'), so it falls just short of full when/when-not guidance.

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