Skip to main content
Glama

Change page properties

wiki_updateMeta
Destructive

Merge page properties, including record key, JSON Schema, and retain.days. A null property removes it. Nested objects are replaced, not deeply merged. Declaration changes do not migrate existing records.

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": {
      "path": "<path>",
      "metadata": "<metadata>",
      "org": "<org>"
    },
    "name": "wiki_updateMeta"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization whose wiki to use. Required on every call, even when only one organization is listed; a path never names it.
pathYesThe wiki's name, a colon, then the page's dot-separated path (general:docs.deploy).
messageNoA brief note on the change describing the change.
replaceNoReplace all metadata instead of merging it.
metadataYesProperties to merge, for example {key: 'id', schema: {type: 'object'}, retain: {days: 30}}.
ifRevisionNoThe page revision returned by wiki_read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already flag this as non-read-only and destructive, and the description adds meaningful behavior beyond that: null removes a property, nested objects are replaced rather than deeply merged, and declaration changes do not migrate existing records. It does not discuss permissions, confirmation, or what happens on partial failure.

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?

The description is four short, front-loaded sentences with no redundant wording. Each sentence adds a distinct semantic rule about merging or metadata behavior.

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?

For a six-parameter mutation tool with nested metadata, the description covers the core merge semantics, removal behavior, and shallow nesting rule well. It does not mention return behavior or success/failure effects, which is a minor gap given there is no output schema.

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 100%, so the baseline is 3, but the description still adds useful meaning beyond the schema by explaining null-property removal and shallow replacement of nested objects. The replace flag is only documented in the schema, so the description does not fully cover every parameter.

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 and resource: merging page properties, including record key, JSON Schema, and retain.days. It is clear what the tool updates, but it does not explicitly distinguish this from content-editing siblings such as wiki_edit or wiki_write.

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 implied by 'Merge page properties' and by the note that declaration changes do not migrate existing records, but there is no explicit guidance on when to use this instead of content-editing or other metadata-related siblings. It also does not state when not to use it.

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.

Resources