Previews

set_preview_password

Set, update, or remove password protection for an existing preview project; leave the password empty to make that preview public.

Instructions

Set, update, or remove password protection for an existing preview project.

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": {
      "slug": "<slug>"
    },
    "name": "set_preview_password"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	The preview slug
`password`	No	Password to set, or empty to make public

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Nov 6, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It signals a mutation with three modes, but says nothing about required permissions, whether rotating the password invalidates existing access or shared links, whether the change is reversible, or how removal is expressed (that detail lives only in the schema).

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 front-loaded sentence with the operation and scope stated first and no filler. Nothing could be removed without losing information.

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 tool with a fully documented schema and no output schema, the description covers the essential purpose and identifies the removal mode. What remains missing is permission/effect context on the mutation, which is a modest gap rather than a blocking one.

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%, so both slug and password already carry their own documentation, including the empty-string-means-public convention. The description adds no format, constraint, or edge-case meaning beyond that, 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?

"Set, update, or remove password protection for an existing preview project" gives a specific verb set and a resource (preview password protection) not covered by any sibling name. It is distinguishable from update_preview at a glance, though it never explicitly names that sibling as the non-alternative.

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: an agent can infer this is the tool for managing a preview's password, but the description never states when to reach for it versus update_preview, nor any prerequisite such as the target preview already existing under the caller's account. No exclusions or alternatives are named.

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

Deploy Server