Skip to main content
Glama

Signal by StackEnhance

Brand email summary

get_brand_summary
Read-onlyIdempotent

A brand's email-marketing profile as observed by StackEnhance Signal: market, category, the date Signal first observed it, marketing emails observed in the last 6 months, current frequency (average emails per week over the last 90 days), the date of the latest observed campaign and, for brands Signal has followed 28+ days in SE, NO, DK, FI or DE, its rank in that market by frequency. Use for questions like "How often does Newport email customers?" or "Is IKEA still sending newsletters?". Without a market, a brand tracked in several countries gets one summary per market. For two or more named brands use compare_brands instead of calling this once per brand. Returns aggregates only — no campaign list, subject lines, offers or creative analysis. Cite each result's details_url as the source.

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>"
    },
    "name": "get_brand_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 / market_rank
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "market": {
      +          "type": "string"
      +        },
      +        "of": {
      +          "type": "integer"
      +        },
      +        "rank": {
      +          "type": "integer"
      +        }
      +      },
      +      "required": [
      +        "rank",
      +        "of",
      +        "market"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so safety is covered; the description goes well beyond that by disclosing aggregate-only output (no campaign list, subject lines, offers, or creative analysis), the one-summary-per-market behavior when no market is given, the 28+ day / SE, NO, DK, FI, DE eligibility condition for rank, and the requirement to cite details_url.

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 what the tool returns, then use cases, then exclusions, then output limits and citation guidance — a logical order. It is a dense single block with long parenthetical clauses (frequency definition, 28+ day rank condition) that slow parsing slightly, but nearly every clause carries actionable 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?

An output schema exists so return structure needn't be explained, and the description still covers output scope (aggregates only), multi-market behavior, the rank eligibility caveat, and sourcing. Nothing an agent needs in order to call this 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 would be 3, but the description adds real meaning: omitting market yields one summary per tracked market, and brand can be a user-written name or a domain. That clarifies the practical consequence of the optional parameter beyond the schema's wording.

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?

The description states a specific verb and resource — a brand's email-marketing profile as observed by StackEnhance Signal — and enumerates the exact contents (market, category, first-observed date, 6-month email count, 90-day frequency, latest campaign date, market frequency rank). It clearly distinguishes itself from the sibling compare_brands by scoping to a single brand.

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?

It gives concrete example questions ("How often does Newport email customers?", "Is IKEA still sending newsletters?") that map directly to this tool, plus an explicit exclusion: for two or more named brands use compare_brands instead of calling this repeatedly. The market-omission fan-out behavior is also spelled out.

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.