Skip to main content
Glama
Sign In
brewpage-mcp

brewpage-mcp

by kochetkov-ma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Set gallery visibility

set_visibility

List or unlist a public publication in the gallery and sitemap while keeping its link unchanged, so you can control discoverability without breaking shared URLs.

Instructions

List or unlist a public publication in the gallery and sitemap. Link unchanged.

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>",
      "listed": "<listed>"
    },
    "name": "set_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPublication ID
typeYesPublication type; only public html, site and file can be listed
listedYestrue = listed, false = unlisted
namespaceYesPublication namespace
ownerTokenNoOwner token from create. Default: env BREWPAGE_OWNER_TOKEN (local server only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.21.0
    • changedInput schema / properties / listed / description
      Previous value: -"false = hide, true = show"New value: +"true = listed, false = unlisted"
  2. Changed1 schema field changedv1.16.3
    • changedInput schema / properties / ownerToken / description
      Previous value: -"Owner token from create. Default: BREWPAGE_OWNER_TOKEN."New value: +"Owner token from create. Default: env BREWPAGE_OWNER_TOKEN (local server only)."
  3. Changed2 schema fields changedv1.15.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  4. Addedv1.13.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so the description must supply the consequences, and it does: it names the surfaces affected (gallery and sitemap) and states the URL is preserved. What is still missing is whether the change is idempotent and what authorization the ownerToken implies, but the core effect of the mutation is disclosed.

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 short sentences with the operation first and the key invariant ('Link unchanged') second; nothing is redundant or 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?

With no output schema and full-schema parameter documentation, the description's remaining job is to convey the effect of the mutation, which it does by naming the affected surfaces and the unchanged link. It falls short only on tie-breaking guidance against sibling visibility/privacy tools.

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%, including the enum on type determining which publications can be listed, so the schema already does the parameter work. The description adds no per-parameter meaning beyond repeating 'listed' semantics that the schema states more precisely (true = listed, false = unlisted).

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 pair of operations ('List or unlist') on a specific resource ('a public publication in the gallery and sitemap'), which is far more informative than the name alone. It implies but never names the sibling it is most likely confused with (make_private), so sibling differentiation is only partial.

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?

The phrase 'public publication' signals the precondition for use and 'Link unchanged' hints this is a discoverability toggle rather than an access-control change, which is useful implied guidance. However, it never explicitly says when to choose this over make_private or search_gallery, nor what to do with a private publication.

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

Deploy Server

Other Tools