Skip to main content
Glama

Make private

make_private
Destructive

Make a public publication private: it gets a new private link, the public link stops working, a custom domain on it is detached. One-way.

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

NameRequiredDescriptionDefault
idYes
typeYes
namespaceYes
ownerTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / id / description
      Removed value: -"Publication ID"
    • removedInput schema / properties / namespace / description
      Removed value: -"Publication namespace; only `public` publications can be made private"
    • removedInput schema / properties / ownerToken / description
      Removed value: -"Owner token from create. Default: env BREWPAGE_OWNER_TOKEN (local server only)."
    • removedInput schema / properties / type / description
      Removed value: -"Publication type"
  2. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds genuinely new behavioral detail on top: a new private link is minted, the existing public link breaks, and any custom domain is detached. It also flags irreversibility. It stops short of stating authorization requirements (the ownerToken parameter) or what the response contains.

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 sentence, front-loaded with the state transition and followed by the three consequences in order of impact, ending with the irreversibility flag. No filler or restatement of the title.

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

Completeness3/5

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

The behavioral half of the definition is well covered for a destructive mutation with no output schema, but the parameter half is entirely absent and no permission or ownership requirement is stated. For a four-parameter, 0%-documented, irreversible operation, that leaves a meaningful gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters (type, namespace, id, ownerToken), and the description says nothing about any of them. An agent must guess what 'namespace' identifies and why 'ownerToken' is optional or required for a destructive operation, so the description fails to compensate for the schema gap.

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 and resource ('Make a public publication private') and enumerates the concrete effects, so an agent knows exactly what state transition occurs. It does not name or contrast any sibling (e.g. set_publication, remove_domain), so differentiation is left to inference.

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 by the purpose: you call this when something is currently public and must stop being public. The trailing 'One-way.' acts as a real usage caveat (irreversible, so treat as a last step), but there is no explicit when-not guidance, no mention of prerequisites such as an owner token, and no pointer to alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.