Skip to main content
Glama

preview_email_audience

Read-onlyIdempotent

Count eligible campaign recipients for all contacts or a tag. The count reflects current consent and suppression records.

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": {
      "audience": "<audience>"
    },
    "name": "preview_email_audience"
  }
}

Input Schema

NameRequiredDescriptionDefault
audienceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond the annotations by saying the count reflects current consent and suppression records, which explains why the number may differ from a raw contact total. It does not cover refresh timing or any rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, with the primary action stated first and the behavioral caveat second. Nothing is redundant, and no sentence could be removed without losing information.

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 single-parameter read-only tool with no output schema and strong annotations, this is nearly complete: it defines the audience domain and clarifies what the returned count means. The only gap is that the return shape, presumably a single integer, and whether a breakdown is included are not stated.

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 0%, so the description has to compensate; it partially does so by naming the two audience variants ('all contacts' or 'a tag') that correspond to the schema's oneOf with const kinds. It adds no detail about tag matching semantics, such as whether the tag name must match exactly or must already exist, so the boolean and tag branch remains under-specified.

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 states a specific verb and resource: it counts eligible campaign recipients, scoped either to all contacts or to a tag. That is enough to distinguish it from siblings such as list_email_campaigns or get_email_performance, although it never names an alternative explicitly.

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 only implied: an agent can infer this is a pre-send sizing check, but the description never says when to call it (before a send, after changing consent settings) or when another tool is the better choice. There are no stated prerequisites or exclusions.

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