Skip to main content
Glama
Sign In

twelvebit Analytics

by app.twelvebit
OverviewDiscussionsAdmin

Add or remove exclusions

update_exclusions
DestructiveIdempotent

Add and remove single entries in the exclusion lists of Settings → Exclusions: ips (addresses or ranges like 203.0.113.0/24), paths (/admin/**), hostnames (staging.example.com), countries (new visits are not recorded) and hidden_countries (also hides the country's past data in every report; nothing is deleted, and removing it from hidden_countries shows the data again). Countries are ISO codes or English names. Example: {"add": {"ips": ["203.0.113.7"]}, "remove": {"countries": ["DE"]}}. Excluded visits are lost for good, so ask the user first. Adding hidden_countries needs confirm: true; without it the tool only describes the change. A repeat changes nothing; pass an idempotency_key to retry safely. change_note says what changed. list_sites shows the current lists.

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": "update_exclusions"
  }
}

Input Schema

NameRequiredDescriptionDefault
addNoEntries to add: ips, paths, hostnames, countries, hidden_countries.
siteNoSite domain (example.com), id or public id (tb_…). Optional with a site key, or when the account has one site.
removeNoEntries to remove: ips, paths, hostnames, countries, hidden_countries.
confirmNoNeeded (true) only when add.hidden_countries is set: hiding past data changes every report.
idempotency_keyNoA fresh UUID for this create. Send the same value when you retry the same call: the first result comes back and nothing is created twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial context beyond the destructive/idempotent annotations: exclusion of visits is irreversible, hidden_countries hides past report data without deleting it and is reversible by removal, the confirm flag turns the call into a dry-run, and repeats are no-ops. That is precisely the behavior an agent needs before a destructive write.

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?

Front-loaded with the verb and resource, and the example plus the safety warning are placed before the mechanics. The long parenthetical about hidden_countries is dense, but no sentence is 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?

For a destructive nested-object mutation with no output schema, the description covers reversibility, confirmation gating, idempotency, and a pointer to list_sites for current state. It leaves open whether add and remove can be combined in one call and does not explain what the response reports.

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 real meaning: a concrete example payload showing the add/remove nesting, the rule that confirm is only needed with add.hidden_countries, and why an idempotency_key exists. Minor ambiguity: change_note is described but is not in the schema, which could confuse an agent about whether it is an input or output field.

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 pair (add/remove) plus the exact resource (entries in the Settings → Exclusions lists) and enumerates the five entry types with examples. An agent can distinguish this from siblings like update_site_settings or list_sites without opening the 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?

Gives clear operating conditions: ask the user first because excluded visits are lost, and adding hidden_countries requires confirm:true or the call only describes the change. It also routes to list_sites to read current lists. It stops short of an explicit 'do not use this for X' exclusion, but the context is unambiguous.

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