Help by DeltaBreen

new_product_key

Destructive

Replace a site's test or live key with a new one. Pages still using the old key stop working at once, so only do this when asked, and update the site straight after.

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": {
      "product_id": "<product_id>"
    },
    "name": "new_product_key"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No	"test" (the default: works on any site, sends no email, counts towards no plan) or "live" (works only on a verified domain).
`product_id`	Yes	The site's id (a uuid), from list_products.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026
- changedInput schema / properties / mode / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
```
First observedOct 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is known. The description adds genuinely non-obvious blast-radius detail — existing pages using the old key fail immediately — which is the key operational consequence.

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?

Two sentences, zero waste, with the effect and the caution front-loaded ahead of the recovery instruction.

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?

Covers what it does, the consequence, and when to call it; with no output schema present, it could have noted that the new key is what comes back, but the essential call-time information is there.

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%, with the mode parameter fully explained in the schema itself (test vs live, verified-domain requirement). The description only alludes to test/live keys without adding format or constraint detail, so baseline 3 applies.

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?

States a specific verb and resource ('Replace a site's test or live key with a new one'), scoped to a single site, which distinguishes it from sibling key-secret tools like new_integration_secret and from update_product.

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?

'Only do this when asked, and update the site straight after' gives an explicit precondition and a required follow-up action. It doesn't name a sibling alternative, but the trigger condition is clear enough to route correctly.

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

All Help by DeltaBreen 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?