brewpage-mcp

Make private

make_private

Destructive

Converts a public publication into a private one, detaching any custom domain and breaking the public link while returning a new private link. Use it to restrict access to published content.

Instructions

Make a public publication private: it gets a new private link and the public link stops working; a custom domain on it is detached. One-way. Returns the new link, namespace and id, plus a new management link when the publication had one; the owner token stays the same.

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": {
      "type": "<type>",
      "namespace": "<namespace>",
      "id": "<id>"
    },
    "name": "make_private"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Publication ID
`type`	Yes	Publication type
`namespace`	Yes	Publication namespace; only `public` publications can be made private
`ownerToken`	No	Owner token from create. Default: env BREWPAGE_OWNER_TOKEN (local server only).

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.21.0Nov 12, 2026

TDQS

A4/5.0

Behavior5/5

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

Substantially exceeds the annotations (destructiveHint=true, readOnlyHint=false) by naming exactly what is destroyed or changed: a new private link is issued, the public link stops working, and any custom domain is detached. It also confirms the owner token is preserved and flags the operation as one-way, which is precisely the context an agent needs before an irreversible mutation.

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

Conciseness4/5

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

Everything is packed into a single sentence that front-loads the operation and its consequences, with no filler. The semicolon-chained clauses around the return values make it slightly dense to parse, but no wording is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description usefully enumerates the returned values (new link, namespace, id, and a management link when one existed). Combined with the irreversibility and side-effect disclosure, this covers everything needed to call a destructive 4-parameter tool 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%, so all four parameters are already documented, including the enum for type and the public-only constraint on namespace. The description only indirectly touches parameters (the owner token staying the same), which adds slight value but does not meaningfully extend the schema.

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 gives a specific verb+resource ('Make a public publication private') and states the precondition that only public publications qualify. It does not explicitly distinguish itself from the sibling set_visibility, so an agent must infer that this is the one-way hardening path rather than a reversible toggle.

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 context is implied by 'Make a public publication private' and reinforced with 'One-way', which warns the agent this cannot be undone. However, no alternative is named and no explicit 'use X instead' routing is offered, leaving the agent to infer that set_visibility is the reversible counterpart.

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