twelvebit Analytics

List visitors

list_people

Read-onlyIdempotent

Visitors seen in the range; sortable by name, visits, timestamps, recorded total time, revenue and profile fields: name (or a friendly name like amber-fox-4821), identity, first source, place, visits, total_time_seconds and revenue. Visits, time and revenue are all-time totals. filter=customers for payers, identified for signed-in users; q searches email or name, or matches an exact visitor id or user id. filters narrows to people with at least one visit in the range that matches every filter (as on the dashboard).

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

Input Schema

Name	Required	Description
`q`	No
`to`	No	Last day, inclusive (YYYY-MM-DD).
`from`	No	First day (YYYY-MM-DD, site time zone). Use with to instead of period.
`site`	No	Site domain (example.com), id or public id (tb_…). Optional with a site key, or when the account has one site.
`sort`	No
`limit`	No	Default 20.
`cursor`	No	Use nextCursor from the preceding response with the same range, filters and sort.
`filter`	No
`offset`	No
`period`	No	Time range. Default 30d. today, yesterday, 24h, 7d, 30d, 90d, 12m, wtd, mtd, ytd, all.
`filters`	No	Only visits that match every filter. A value is "is": {"country": "US"}; a list is "is any of": {"country": ["PT", "ES"]}; an object picks the operator: {"page": {"contains": "/blog"}}, {"channel": {"is_not": ["Direct", "Email"]}}, {"page": {"not_contains": "/admin"}}. Operators: is, is_not, contains, not_contains (case-insensitive). "visitor" is "new" or "returning". "ad" is an ad campaign as "google:<campaign id>" or "meta:<campaign id>" (the visits that the Ads page counts for it). Use "(none)" for empty values; countries take ISO codes or English names.
`sort_dir`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 28, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "Use nextCursor from the preceding response with the same range, filters and sort.",
+  "maxLength": 3000,
+  "type": "string"
+}

changedInput schema / properties / sort / enum

Previous value: -[
-  "recent",
-  "revenue"
-]New value: +[
+  "recent",
+  "person",
+  "location",
+  "source",
+  "visits",
+  "first_seen",
+  "last_seen",
+  "revenue",
+  "total_time",
+  "email",
+  "user_id",
+  "device",
+  "browser",
+  "os"
+]

addedInput schema / properties / sort_dir

Added value: +{
+  "enum": [
+    "asc",
+    "desc"
+  ],
+  "type": "string"
+}

First observedOct 23, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds meaningful nuance: visits, time and revenue are all-time totals even though the range scopes which visitors are returned. The filter semantics are also described in enough detail to set expectations for matching behavior.

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 content is dense but relevant. However, it is a single long sentence with some repetition of fields like visits and revenue, making it harder to scan than it could be.

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 12-parameter tool with nested filters and no output schema, the description covers the core query semantics and likely returned profile fields well. Pagination and output details are mostly delegated to schema descriptions, so it is largely complete but not fully self-contained.

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 58%, but the description compensates substantially by explaining q search behavior, filter modes, sort fields, and the detailed filters object semantics. Some gaps remain around sort_dir, offset, and the default sorting behavior, but the most complex parameters are meaningfully clarified.

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 description clearly establishes that this lists visitors/people seen in a time range and enumerates sortable/profile fields, so the resource and operation are understandable. However, it never explicitly differentiates itself from sibling listing or analytics tools such as get_breakdown, so it stops short of a 5.

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?

It documents useful filters like filter=customers/identified and explains q and filters behavior, which implies when to use the tool for visitor-level lookup. It does not explicitly say when to choose this over alternatives such as get_breakdown or saved segments, leaving usage guidance partly inferred.

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

All twelvebit Analytics tools Inspect

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

Need Help?