Skip to main content
Glama

The world according to capital

Newsletter subscriber stats

newsletter_stats
Read-only

The newsletter's subscriber counts, as totals only: no email address and no single subscriber's row. Returns subscribers (active = confirmed and still subscribed, pending = waiting on the confirmation link, unsubscribed), agent_inboxes (active and pending readers whose address is at an inbox built for agents: agentmail.to), active_by_source (the signup form: subscribe, footer, bookmarks, home, collection, archive, agent, mcp, unknown), and over the last days (default 28, at most 365, UTC, today included): confirmed.total, confirmed.daily (one row a day), confirmed.by_landing_path (the page the form was on, top 50), confirmed.by_utm_source (the utm_source of the link that brought the reader, when the page address carried one) and unsubscribes. (none) counts rows with no value; (other) counts values that are no page address or campaign token. Curator only.

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

Input Schema

NameRequiredDescriptionDefault
daysNoThe window in days, today included (UTC).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's added value is the privacy guarantee (no email addresses, no individual rows), the 'Curator only' authorization requirement, the UTC accounting convention with today included, and the meaning of the (none)/(other) buckets. These are genuine behavioral facts not present in structured fields.

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 content is dense and information-rich, but it is delivered as one long chain of parenthetical enumerations with the most important constraint (totals only, no PII) placed awkwardly after the noun phrase. It is readable but not well structured or cleanly front-loaded.

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 explaining return values, and it does so thoroughly: subscribers, agent_inboxes, active_by_source, and the time-windowed confirmed/unsubscribes fields with their bucket semantics. A reader could interpret the response correctly, though the enumeration is harder to parse than it needs to be.

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% and the single `days` parameter already documents its window, default, and bounds. The description restates default 28, max 365, UTC, today included, adding emphasis but no new semantics beyond the schema.

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 a specific resource (the newsletter's subscriber counts) and an explicit scope constraint: totals only, no email addresses and no per-subscriber rows. That distinguishes it from any row-level listing, though it does not name a sibling tool by name.

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 rather than stated: an agent can infer this is the aggregate-reporting tool, and 'Curator only' flags a permission prerequisite. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative.

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