Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

epicgames_free_promotions

Retrieve current and upcoming Epic Games Store free promotions by locale and country, including promotion windows and offer details for accurate deal checks.

Instructions

Get Epic Games Store free promotions. Returns the store's current and upcoming promotion offers for the requested locale and country. The response preserves the upstream Catalog searchStore payload and its promotion windows; a zero price alone does not mean an offer is part of a limited-time promotion.

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
localeNoStore locale
countryNoTwo-letter country code
allowCountriesNoComma-separated country codes accepted by the upstream promotion query; defaults to country

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that both current and upcoming promotions are returned, that the upstream Catalog searchStore payload and promotion windows are preserved, and that a zero price does not by itself indicate a limited-time promotion. It says nothing about rate limits, auth, result size, or pagination, which are material for an unannotated read tool.

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?

Three sentences, front-loaded with the purpose before the return semantics and the caveat. Every sentence carries information, though 'preserves the upstream Catalog searchStore payload' is jargon that a caller may not parse without domain knowledge.

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

Completeness3/5

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

For a zero-required-parameter read tool with no output schema and no annotations, the description covers purpose and offers a caution about interpreting results, but leaves the returned shape vaguely characterized and omits pagination and volume expectations. Adequate to make a first call, thin for interpreting or scaling the results.

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 all three parameters are documented (locale, country, allowCountries with its default). The description restates the locale/country scoping but adds no format examples or precedence rules beyond what the schema already supplies, so the baseline of 3 applies.

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: 'Get Epic Games Store free promotions', and narrows the scope to 'current and upcoming promotion offers for the requested locale and country'. It does not explicitly distinguish itself from similarly shaped promotion tools (fanduel_sportsbook_promotions, kfc_promotions), but the brand and 'free promotions' framing make its domain unambiguous.

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: fetch free promotions for a locale/country. There is no explicit when-to-use versus when-not, no stated alternative tool, and no note about how to page through or iterate results. The closing caveat about zero price is closer to result interpretation guidance than invocation guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools