Skip to main content
Glama

Change page data settings

configure_page_data
Destructive

Turn Page data on (state: {}), off (state: null, entries are kept) or change its settings; only what state names changes. A private list that holds visitors' entries cannot become shared.

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": {
      "state": "<state>"
    },
    "name": "configure_page_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
stateYes`{collections: {<name>: {mode: 'private'|'shared', write?: 'author'}}}`
manageUrlNoManagement link; replaces namespace, id and ownerToken
namespaceNo
ownerTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 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"
    • changedInput schema / properties / manageUrl / description
      Previous value: -"The page's private management link (https://brewpage.app/manage/...#k=...); stands in for namespace, id and ownerToken."New value: +"Management link; replaces namespace, id and ownerToken"
    • removedInput schema / properties / namespace / description
      Removed value: -"Publication namespace"
    • removedInput schema / properties / ownerToken / description
      Removed value: -"Owner token from create. Default: env BREWPAGE_OWNER_TOKEN (local server only)."
    • removedInput schema / properties / state / anyOf
      Removed value: -[
      -  {
      -    "additionalProperties": {},
      -    "propertyNames": {
      -      "type": "string"
      -    },
      -    "type": "object"
      -  },
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / state / description
      Previous value: -"Settings to change, same shape as `state` on create: `{collections: {<name>: {mode, ...}}}`"New value: +"`{collections: {<name>: {mode: 'private'|'shared', write?: 'author'}}}`"
    • addedInput schema / properties / state / type
      Added value: +[
      +  "object",
      +  "null"
      +]
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already flag destructiveHint=true, and the description earns extra credit by explaining what survives that destruction: disabling keeps entries, only the settings named in `state` change, and a private list with visitor entries cannot be converted to shared. What it omits is authorization or scoping behavior for the id/namespace/ownerToken path.

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 dense sentences with the enable/disable contract front-loaded and the restriction as a closing caveat. The semicolon-compressed phrasing is efficient and every clause carries information, though it reads terse enough that the parenthetical literals are easy to skim past.

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?

For a destructive mutation with no output schema, the description covers the highest-risk behavior (data retention on disable, partial-update scope) but not how the target page is identified or what a successful response looks like. Given five parameters and only 40% schema coverage, more of the scoping surface should be described.

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?

With 40% schema coverage across five parameters, the description does real work on the required `state` parameter by giving literal on/off forms and partial-update semantics. However, `id`, `namespace`, and `ownerToken` are undocumented in both the schema and the description, leaving the identity/scoping half of the call unspecified.

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 uses concrete verbs and resources: turn Page data on, off, or change its settings. It is clear what the tool does, but it does not distinguish itself from the sibling set_page_data, whose name suggests a nearly identical operation, so an agent still has to guess which to call.

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 three usage modes (enable with `state: {}`, disable with `state: null`, or change settings) are spelled out, which implies when to call it. There is no explicit when-not guidance and no routing to set_page_data, delete_page_data, or get_page_data, which are the obvious alternatives for overlapping work.

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.