Skip to main content
Glama

OpenPanel: Get unique users

openpanel_get_unique_users
Read-only

Retrieve unique user and visitor counts for a site over a selected time period via the Insights API to measure audience reach.

Instructions

[UNIFIED] Get unique user/visitor count for a time period via Insights API.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>"
    },
    "name": "openpanel_get_unique_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
date_rangeNo30d
project_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations only declare readOnlyHint=true, which is already visible to the agent. The description adds nothing about the metric definition (unique by user, visitor, session or device), whether counts are approximate or deduplicated, or any pagination/rate-limit behavior — material gaps for a read analytics tool with no output schema.

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?

It is a single short sentence with the verb and scope front-loaded, so there is no padding. However, the unexplained '[UNIFIED]' tag consumes part of an already minimal description without helping an agent decide or call correctly.

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

Completeness2/5

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

For a three-parameter analytics tool with zero schema description coverage and no output schema, the description is too thin: it omits parameter meanings, the definition of 'unique', and any expected response shape, leaving an agent to guess.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters. The phrase 'for a time period' loosely signals that date_range controls the window, but nothing explains the accepted format (the schema default '30d' is the only hint), what 'site' means, or the role of project_id.

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?

Names a specific verb and resource ('Get unique user/visitor count') and scopes it to a time period, so an agent knows the basic operation. It does not distinguish this from the many sibling analytics endpoints (event_count, page_views, overview_report), and the '[UNIFIED]' prefix is unexplained jargon.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no statement of when another OpenPanel analytics tool would be a better choice, and no prerequisites such as needing a site identifier or project context.

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

Deploy Server

Other Tools