Skip to main content
Glama

Brand email frequency

get_brand_email_frequency
Read-onlyIdempotent

How many marketing emails a brand sent in a calendar period, and when, as observed by StackEnhance Signal (ecommerce brands, mostly in Sweden, Norway, Denmark, Finland and Germany). Use for questions like "How many emails did Newport send in August 2026?", "What did Newport send last week?" or "What has X sent recently?". Without a market, a brand tracked in several countries gets one result per market. To compare several brands over the same period, use compare_brands with from and to. Resolve relative dates yourself to YYYY-MM-DD: "last week" is the previous Monday–Sunday, "last month" the previous calendar month, "recently" the last 14 days. Dates are the brand's local calendar dates. The period must start within the last six months (older history is in a Signal account) and may span up to two years. Returns the count; for periods of up to 31 days also the date of each send; and at most two subject lines, only ones already shown on the brand's public StackEnhance page and sent in the period. Every listed send was captured in full; a send without a quoted subject is listed in sends_with_subject_in_signal because its subject is withheld by that limit, not missing. Counts are de-duplicated marketing sends (welcome, birthday and transactional emails excluded). There is no open, click or revenue data. Full campaigns, other subject lines, offers, products and creative analysis are not available through this tool. Cite each result's details_url as the source and as where the full campaigns are.

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": {
      "brand": "<brand>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "get_brand_email_frequency"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesLast day of the period, inclusive, YYYY-MM-DD.
fromYesFirst day of the period, YYYY-MM-DD.
brandYesBrand name as the user wrote it, e.g. "Newport" or "IKEA". A domain such as newport.se also works.
marketNoCountry of one storefront as a two-letter code (SE, NO, DK, FI, DE) or its name ("Sweden"). Omit it to get every market the brand is tracked in.

Output Schema

NameRequiredDescriptionDefault
resultsYes
unavailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / results / items / properties / observed_last_6_months
      Added value: +{
      +  "description": "Marketing emails from this brand that StackEnhance Signal holds from the last 6 months — what details_url leads to.",
      +  "type": "integer"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, and the description adds substantial context beyond them: the six-month lookback window, the two-year maximum span, de-duplication rules (welcome/birthday/transactional excluded), the two-subject-line cap and why some sends appear without subjects, and the explicit absence of open/click/revenue data. The only gap is pagination or rate/volume limits, which are not mentioned.

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?

Front-loaded with purpose and examples, then scope constraints, then output limits — a logical order with no filler. It is dense and long, and a few clauses about returned subject lines overlap what the output schema already covers, but each sentence carries operational information.

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

Completeness5/5

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

For a read-only analytics tool with an output schema, the description covers everything an agent needs: date window limits, relative-date resolution, market behavior, de-duplication definition, unavailable metrics, and citation guidance pointing at details_url. Nothing required to call it correctly is missing.

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 100%, so the baseline is 3, but the description adds real meaning: omitting market yields one result per market rather than a single blended answer, dates are the brand's local calendar dates, and relative expressions must be resolved by the caller. That goes beyond the schema's field-level definitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource+scope: how many marketing emails a brand sent in a calendar period and when, sourced from StackEnhance Signal. It also names the geographic coverage and explicitly separates itself from compare_brands, so an agent can pick it without opening schemas.

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

Usage Guidelines5/5

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

Gives concrete example questions the tool answers, explains what happens when market is omitted (one result per market), points to compare_brands with from and to for multi-brand comparison, and specifies how to resolve relative dates. Explicit when-to-use and when-to-use-something-else guidance.

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