Camden Tools

Get product promotions

get_product_promotions

Read-only

Active promotions that apply to one SKU (discounts, free gifts, end dates).

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": {
      "sku": "<sku>"
    },
    "name": "get_product_promotions"
  }
}

Input Schema

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.

Output Schema

Name	Required	Description	Default
`sku`	Yes
`promotions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 22, 2026
- removedOutput schema / properties / promotions / items / properties / description / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / promotions / items / properties / description / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / promotions / items / properties / discount_value / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / promotions / items / properties / discount_value / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / promotions / items / properties / ends_at / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / promotions / items / properties / ends_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / promotions / items / properties / terms_url / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / promotions / items / properties / terms_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedSep 25, 2026

changedOutput 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"
+}

First observedSep 19, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds that only *active* promotions are returned, which is useful behavioral context, but says nothing about result size, whether an empty result is possible, or locale-dependent behavior beyond what the schema states.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact clause with the scoping constraint ('one SKU') and the payload contents front-loaded. Nothing is redundant and nothing needs trimming.

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?

For a simple two-parameter read tool with an output schema, a full-annotation safety profile and fully documented parameters, only the routing relative to get_cart_promotions is missing. Otherwise an agent has what it needs to call it correctly.

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%: both sku and locale are documented in the schema, including the default locale and its effect on names and prices. The description only restates SKU scoping, so baseline 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?

States a specific resource (promotions) and scope (active, applying to one SKU), and enumerates what is returned: discounts, free gifts, end dates. This clearly separates it from cart-level or catalogue-wide tools, though it never names the closest sibling (get_cart_promotions) explicitly.

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?

The 'one SKU' scoping implies this is the product-level lookup rather than a cart-level one, but there is no explicit when-to-use or when-not-to-use statement, nor any note about prerequisites such as needing an active storefront context.

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

All Camden Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?