Skip to main content
Glama

Write author entries

set_page_data
DestructiveIdempotent

Create or replace 1-20 author entries in one list, each by key; visitors' entries stay untouched.

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": {
      "collection": "<collection>",
      "docs": "<docs>"
    },
    "name": "set_page_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
docsYes
manageUrlNoManagement link; replaces namespace, id and ownerToken
namespaceNo
collectionYes
ownerTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / collection / description
      Removed value: -"List (collection) name"
    • removedInput schema / properties / docs / description
      Removed value: -"Entries to write, 1-20"
    • changedInput schema / properties / docs / items / properties / key / description
      Previous value: -"Entry name: 1-128 letters, digits, _ . -, not starting with _"New value: +"1-128 letters, digits, _ . -, not starting with _"
    • removedInput schema / properties / docs / items / properties / value / description
      Removed value: -"The entry's JSON value, typically an object"
    • 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)."
  2. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description reinforces idempotency via 'create or replace ... each by `key`'. The clause 'visitors' entries stay untouched' is genuine added value that bounds the blast radius of the destructive write. It says nothing, however, about the authorization model implied by namespace/ownerToken/manageUrl, which matters for a destructive write.

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?

One sentence, front-loaded with the action and scope, with the safety-relevant caveat trailing. No filler or redundant restatement of the tool name.

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

Completeness2/5

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

With six parameters, low schema coverage, and a destructive write annotated only by boolean hints, the description should clarify how the target collection is identified (namespace/id/ownerToken versus a single manageUrl). That ambiguity is the main thing an agent can get wrong here and is left entirely to the schema.

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 only 17%, so the description must compensate, and it largely does not. It clarifies `key` semantics and the 1-20 range (which the schema already encodes via minItems/maxItems), but leaves `collection`, `namespace`, `ownerToken`, and `id` unexplained — including the critical fact that `manageUrl` replaces namespace, id and ownerToken.

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?

States a specific verb pair ('create or replace') and resource ('author entries in one list'), plus the keying rule ('each by `key`'), so an agent knows this is a keyed upsert rather than a wholesale overwrite. It stops short of naming how this differs from siblings like configure_page_data or set_kv.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The '1-20 entries in one list' phrasing implies a bounded batch-upsert use case, but the agent must infer that set_page_data is for author-scoped data rather than visitors' data or configuration.

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.