Skip to main content
Glama

epicgames_free_promotions

Read-only

Read the Epic Games Store's public regional free-promotions feed and return the upstream Catalog.searchStore offer records for one storefront region: each offer's offerId, namespace, title and promotion window arrays (active and upcoming), plus the native paging metadata. locale selects localized text (default en-US), country selects the two-letter storefront region (default US) and allow_countries forwards the upstream comma-separated country allow-list (defaulting to country); invalid codes are rejected instead of silently defaulted. The source may include upcoming as well as active offers, so check each offer's promotion start and end fields before describing it as currently redeemable; a zero price alone does not mean an offer is part of a limited-time promotion. This is promotion metadata only — it never claims, redeems or purchases an offer.

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

Input Schema

NameRequiredDescriptionDefault
localeNoOptional store locale, default en-US. Must match the source locale shape (2-3 letter language plus optional subtags), for example en-US.
countryNoOptional two-letter storefront country code, default US. Selects the region whose promotion windows are returned.
allow_countriesNoOptional comma-separated country codes forwarded as the upstream allowCountries parameter, for example US or US,CA. Omitted it defaults to the selected country. This is the upstream allow-list, not a local filter.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuine behavior beyond them: invalid locale/country codes are rejected rather than silently defaulted, results are upstream passthrough records, and upcoming offers may be mixed in with active ones. It stops short of describing error shapes or rate/limit behavior, but the added disclosure is substantial.

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?

It is a single dense paragraph that front-loads the purpose and then layers scope, interpretation caveats, and parameter defaults; each clause carries information. It runs long and the caveats could be tightened, but there is no filler or repetition.

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 an output schema present, return values need no deep explanation, and the annotations plus 100% schema coverage carry most of the rest. The description covers region scoping, defaults, validation behavior, and interpretation caveats; the only minor gap is that 'native paging metadata' is mentioned without any hint of how paging is expressed or whether all pages are returned.

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 coverage is 100%, so the schema already documents all three parameters including defaults and format examples. The description only adds the invalid-code rejection behavior and clarifies that allow_countries is the upstream allow-list rather than a local filter, which is useful but marginal against a fully documented schema.

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 names a specific verb and resource ('Read the Epic Games Store's public regional free-promotions feed') and enumerates the returned record shape (offerId, namespace, title, active/upcoming promotion window arrays, paging metadata) scoped to one storefront region. An agent can immediately tell this fetches raw promotion metadata rather than, say, article or sportsbook content.

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

Usage Guidelines4/5

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

It gives real operating guidance: check promotion start/end fields before calling an offer currently redeemable, note that a zero price alone doesn't imply a limited-time promotion, and states the tool never claims, redeems or purchases. These act as usage and scope boundaries, though there is no explicit routing statement to alternative tools.

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.