Help by DeltaBreen

set_domain_products

Idempotent

Choose which sites' forms are on a domain. This replaces the list. Owner only.

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": {
      "domain_id": "<domain_id>",
      "product_ids": "<product_ids>"
    },
    "name": "set_domain_products"
  }
}

Input Schema

Name	Required	Description	Default
`domain_id`	Yes	The domain's id (a uuid), from list_domains.
`product_ids`	Yes	The sites whose form is on this domain (ids from list_products). This replaces the list.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations declare idempotentHint=true and destructiveHint=false, and the description corroborates the idempotent behavior by stating the list is replaced wholesale rather than appended. Crucially it adds the "Owner only" authorization requirement, which annotations do not cover. It stops short of saying what happens to sites dropped from the list, but the added permission context is genuine value.

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?

Three short sentences, zero filler, with the core operation stated first and the two critical caveats (replacement, owner-only) immediately after. Nothing is buried.

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 two-parameter mutation with full schema coverage and existing annotations, the description covers what changes, that it is a full replacement, and who may call it. It omits the fate of de-associated forms and the response shape, but with only two required params and no output schema the remaining gap is minor.

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 both parameters including the uuid source and the replacement semantics. The description's "which sites' forms are on a domain" merely restates product_ids and does not add format detail, 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?

The description states a specific verb-plus-resource: setting which sites' forms belong to a domain. That is clearly distinct from add_product/remove_product/update_product siblings by virtue of being a bulk assignment, though no sibling is named explicitly. An agent can identify the operation but must infer which neighbors it replaces.

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?

"This replaces the list" signals the replace-vs-incremental distinction, which is the key usage decision against add/remove-style siblings. "Owner only" flags the permission precondition. However, no alternative tool is named and no explicit when-not guidance is given, leaving the choice of this tool versus per-product operations to inference.

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?