Skip to main content
Glama

Meta Council

by com.meta-council
OverviewDiscussionsAdmin

Get Site Analytics

get_site_analytics
Read-onlyIdempotent

OPERATOR ONLY: visitor traffic for the META COUNCIL PLATFORM's own website — every visitor added together, NOT the caller's workspace (use get_workspace_metrics for that) and NOT the business rollup (use get_meta_council_platform_metrics for that). Requires both the platform:admin scope AND an ADMIN_EMAILS operator account; everyone else gets a permission error naming which of the two requirements failed. Covers a window of whole UTC days ending today, set by days. Returns human total views, unique visitors, the authenticated/anonymous split, the busiest public paths, the busiest in-app sections, top referrers and a per-day series, separate bot page/section view counts, plus the window it covers so the caller need not track what it asked for. Page paths and in-app sections are counted separately and are not comparable to one another. It never returns per-visitor rows, email addresses, IP hashes, user agents, session identifiers or query text — the rollup reports how many, never who. Also returns recorded account activation cohorts by creation-event source and signed-in weekly distinct account/section usage. These are prospective observations, not visitor conversion: campaign attribution, visit-to-account conversion and visit entry pages are explicitly unavailable. No named account activity is returned. Optional digest_limit includes retained weekly aggregate snapshots and delivery counts; digest_before_week pages strictly before a scheduled Monday YYYY-MM-DD. This read never captures or sends a digest.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoWhole UTC days to cover, ending today. Defaults to 7.
digest_limitNo
digest_before_weekNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / digest_before_week
      Added value: +{
+  "pattern": "^[0-9]{4}-[0-9]{2}-[0-9]{2}$",
+  "type": "string"
+}
    • addedInput schema / properties / digest_limit
      Added value: +{
+  "maximum": 52,
+  "minimum": 1,
+  "type": "integer"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "text": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "text"
-  ],
-  "type": "object"
-}New value: +null
  3. Added

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, but the description goes well beyond: dual auth requirements with an error that names the failing requirement, privacy guarantees (no per-visitor rows, emails, IP hashes, user agents, sessions, query text), the unavailable metrics (attribution, conversion, entry pages), and that digest_limit only reads snapshots and never captures/sends a digest.

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?

Dense but front-loaded — the OPERATOR ONLY scope and sibling differentiation come first, and the exclusions follow. It is long, but almost every clause carries operative information (auth, privacy, unavailable metrics) rather than filler.

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 only 33% parameter coverage, the description fully enumerates the return payload (views, uniques, auth/anonymous split, paths, sections, referrers, per-day series, bot counts, activation cohorts) and warns that paths and sections are not comparable. Nothing an agent needs to call or interpret it 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 only 33%, and the description compensates: it explains days as a whole-UTC-day window ending today, digest_limit as retained weekly aggregate snapshots with delivery counts, and digest_before_week as paging strictly before a scheduled Monday. It does not restate the min/max bounds, which the schema already carries.

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+resource (visitor traffic for the platform's own website) and immediately distinguishes itself from both get_workspace_metrics and get_meta_council_platform_metrics by naming them. An agent can select this tool correctly 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?

Explicit when-to-use ('OPERATOR ONLY', platform's own site) plus two named alternatives with their selecting conditions. Also states the precondition (platform:admin scope AND ADMIN_EMAILS operator account) and what happens otherwise.

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

All Meta Council 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