Skip to main content
Glama

Tally by Outpost

List visitors

list_visitors
Read-onlyIdempotent

Visitors (visits on a cookieless site) of a period, most recent first or by revenue or likely to buy, with visits, pages, engaged time per visit, revenue and their latest visit.

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_visitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoA custom range's last day (YYYY-MM-DD), with from.
fromNoA custom range's first day (YYYY-MM-DD), with to. Up to 366 days, not past today.
siteNoThe site's id. Optional: the API key's site is the one read.
sortNorecent (default), revenue, or likely to buy.
limitNoRows at most (default 25).
cursorNoThe next_cursor of the previous page, to read on.
periodNoA preset period, in the site's time zone. Leave out for the tool's default, or give from and to instead.
filtersNoVisits that match every filter (AND). Each dimension at most once.
customers_onlyNoOnly visitors with a purchase.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds useful context beyond that – cookieless data source, per-visit engaged time, latest visit included – but says nothing about pagination behavior, the default period, or how many rows are typical, which matters for a 25-row-capped list.

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?

One dense sentence, front-loaded with the resource and followed by ordering and returned metrics; nothing is redundant. The fragmentary grammar ('Visitors ... of a period') and the trailing metric list make it slightly harder to parse than it needs to be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, naming the returned fields (visits, pages, engaged time, revenue, latest visit) is genuinely valuable compensation. However, a 9-parameter tool with a nested 19-key filters object deserves at least a sentence on filtering (AND semantics, one value per dimension) and on pagination, neither of which the description supplies.

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 every parameter, including the nested filters, is already documented in the schema; baseline 3 applies. The description adds only marginal meaning, mainly reinforcing the sort options and the returned fields rather than explaining period/cursor/filter interaction.

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?

States the resource (visitors on a cookieless site), the scoping (of a period), the ordering options, and the metrics returned, so an agent knows exactly what comes back. It stops short of distinguishing itself from the sibling get_visitor (single visitor) and list_sales, and it is a noun fragment rather than an explicit verb+resource statement.

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?

Usage is implied through the sort enum ('most recent first or by revenue or likely to buy') and the period scoping, which hints at analysis-oriented listing. There is no explicit when-to-use versus when-not guidance, and no pointer to get_visitor for a single visitor or to get_breakdown for aggregate metrics.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources