Skip to main content
Glama

Change publication settings

set_publication
DestructiveIdempotent

Change settings of a publication; only the arguments sent change. Badge and title need the owner token in a BrewPage profile.

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": "set_publication"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
typeYes
titleNo1-200 characters; empty = the title from the content
extendNotrue = keep it for the longest time the profile allows
listedNoListed in the gallery and sitemap (public html, site, file)
passwordNo`null` removes it
namespaceYes
ownerTokenNo
badgeHiddenNoHide the BrewPage badge; up to 5 per profile
deliveryModeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, destructive, idempotent mutation, so the safety profile is covered. The description adds two pieces of context the annotations do not carry: patch semantics (unsent fields are preserved) and an authorization requirement (badge and title changes require the owner token in a BrewPage profile). It does not explain what the destructive aspect actually affects.

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?

Two short clauses, front-loaded with the core action and patch semantics before the authorization caveat; nothing is redundant. The second clause is slightly compressed ('in a BrewPage profile') but does not waste space.

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?

With 10 parameters, 50% schema coverage, no output schema, and a destructive mutation, the description covers the two highest-risk items (partial update, token requirement) but leaves most of the surface undocumented. An agent still lacks guidance on what changing deliveryMode or listed implies for existing URLs and visibility.

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

Parameters4/5

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

Schema coverage is only 50%, and the description compensates by clarifying the meaning of ownerToken (required for badge and title) and the overall partial-update contract for all optional fields. It still leaves namespace, deliveryMode, extend, and how type+namespace+id jointly identify the target unexplained, so it does not fully close the coverage 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 states a specific verb+resource ('Change settings of a publication') and immediately establishes patch semantics, so an agent knows this mutates an existing publication rather than creating or publishing one. It does not name or contrast with close siblings (make_private, set_domain, update_html), so it falls short of full sibling differentiation.

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?

'Only the arguments sent change' gives useful implied guidance that this is the partial-update entry point, which is the main when-to-use signal. There is no explicit statement of when to prefer this over make_private, set_domain, or the publish_*/update_* tools, and no prerequisites or exclusions are given.

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.