get_product_promotionsActive promotions that apply to one SKU (discounts, free gifts, end dates).
| Name | Required | Description | Default |
|---|---|---|---|
| sku | Yes | Product SKU exactly as shown on the site. | |
| locale | No | Storefront locale such as en-GB (default), en-US, de, fr-FR, es-ES, it-IT, nl-NL, pl. Controls product names, slugs and prices. |
| Name | Required | Description | Default |
|---|---|---|---|
| sku | Yes | ||
| promotions | Yes |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "promotions": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "brands": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "description": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "discount_value": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "Percent or amount off, depending on type."
+ },
+ "ends_at": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "free_gift": {
+ "anyOf": [
+ {
+ "additionalProperties": false,
+ "properties": {
+ "name": {
+ "type": "string"
+ },
+ "sku": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "sku",
+ "name"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "id": {
+ "type": "number"
+ },
+ "name": {
+ "type": "string"
+ },
+ "scope": {
+ "type": "string"
+ },
+ "terms_url": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "type": {
+ "description": "percentage_discount, fixed_discount or free_gift.",
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "name",
+ "description",
+ "type",
+ "discount_value",
+ "ends_at",
+ "scope",
+ "brands",
+ "free_gift",
+ "terms_url"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "sku": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "sku",
+ "promotions"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds that promotions are 'active' and includes 'end dates', which is useful. Since openWorldHint=true is also present, the description could have noted that results are not exhaustive, but it doesn't. Overall, it adds moderate context beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is one clear, concise sentence that packs all essential information: active promotions, single SKU scope, and examples of what is included. It is front-loaded with the purpose and is efficient with no fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple with only two parameters, a full schema, and an output schema. The description adequately covers the purpose and key details. The only minor gap is not stating that the output is limited to active promotions only (though 'active' is implied). Given the output schema likely documents return structure, the description is sufficient for an agent to call correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so parameters are well documented. The description doesn't repeat schema details but mentions 'discounts, free gifts, end dates' which hints at the type of data returned, complementing the schema. It doesn't add new semantics for the 'locale' parameter, but the schema already covers that. Since the schema covers everything, the description's contribution is minimal but acceptable.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool as returning active promotions for a single SKU, with specific examples of promotion types (discounts, free gifts, end dates). It is distinguishable from the sibling 'get_cart_promotions' which focuses on cart-level promotions. However, it doesn't explicitly compare with any sibling to avoid confusion.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies it is for SKU-level promotions, and the sibling 'get_cart_promotions' likely handles cart-level, but there is no explicit guidance on when to use this tool versus alternatives. No exclusions are stated, and the usage context is left to the agent to infer from the resource type.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.