Skip to main content
Glama
Sign In

twelvebit Analytics

by app.twelvebit
OverviewDiscussionsAdmin

Usage this month

get_usage
Read-onlyIdempotent

Events this month (UTC) by type: page views, goals, pings, bot hits and others; the billable count (page views + goals) against the plan tiers; the top paths and hostnames by event count; and the usage controls in place (excluded paths and hostnames, drop_pings, pageview_sample_rate). Use it to find what drives volume before you suggest a control.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoSite domain (example.com), id or public id (tb_…). Optional with a site key, or when the account has one site.
monthNoYYYY-MM. Default this month.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly/idempotent/non-destructive, so the safety bar is low, yet the description adds real value: UTC time basis, the definition of the billable count (page views + goals), and an inventory of which controls are reported. It doesn't state how many top paths are returned or the response shape, which keeps it from a 5.

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?

Two sentences, front-loaded with the resource and scope, then a clear action-oriented directive. The first sentence is a dense clause chain, but every clause carries distinct content rather than filler.

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?

With no output schema, the description carries the burden of describing returns and does so concretely (event types, billable count vs tiers, top paths/hostnames, active controls). Minor gaps remain on cardinality of 'top' lists and whether excluded paths are returned verbatim, but an agent has enough to call it correctly.

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 coverage is 100%, so both parameters are fully documented in structured fields; baseline is 3. The description reinforces the 'this month' default and adds a UTC framing, but says nothing about the `site` parameter's optionality or the month override, so it adds only marginal meaning.

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?

Specific verb/resource: usage events this month broken down by type, plus billable count against plan tiers, top paths/hostnames, and current usage controls. The enumerated return content makes it clearly distinguishable from siblings like get_breakdown, get_overview, and get_billing 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 Guidelines4/5

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

Explicit when-to-use: 'Use it to find what drives volume before you suggest a control,' which routes the agent toward update_exclusions as the follow-up. No explicit when-not or named alternative tool, so it stops short of a 5.

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

All twelvebit Analytics 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