Skip to main content
Glama
Sign In

LivePage · 活页

by com.24haowan
OverviewDiscussionsAdmin

Switch live version

publish_version
Destructive

Make an approved version that is waiting to publish live, or roll back to an earlier approved version. Existing versions and comments remain. Call only after the user explicitly approves publishing or rolling back. Approved uploads without hold may already have become live. quiet=true makes this switch notify no one (workspace people or subscribers); releasing a held version keeps the quiet choice made at upload unless you pass it. Keywords: publish · web page · webpage · link · share · share to WeChat · WeChat link · html · pdf · markdown · upload · LivePage · proposal.

Input Schema

NameRequiredDescriptionDefault
tagNoOptional: the tag this version gets when it goes live (a string = the tag name, such as 2026-10-28 / v2 final; or {name, title, note}). On a tagged page readers see the newest tagged version and can browse every tagged one (past issues); an existing tag name moves to this version. Daily reports use the day's date. Omitted: a page that has never been tagged behaves exactly as today; on a tagged page this version takes over the tag readers are looking at
noteNoWhat changed this time: one line for subscribers and teammates, 20 characters or fewer, for example “Revised pricing after client feedback”. It appears in the update reminder; without it the reminder only says the version number, and the platform will not make one up.
quietNotrue = no notification this time: when this version goes live, neither workspace people nor readers subscribed to this page are notified; subscribers are notified as usual on the next update. Use it for small edits such as typo fixes
version_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tag
      Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 40,
+      "minLength": 1,
+      "type": "string"
+    },
+    {
+      "properties": {
+        "name": {
+          "maxLength": 40,
+          "minLength": 1,
+          "type": "string"
+        },
+        "note": {
+          "maxLength": 2000,
+          "type": "string"
+        },
+        "title": {
+          "maxLength": 200,
+          "type": "string"
+        }
+      },
+      "required": [
+        "name"
+      ],
+      "type": "object"
+    }
+  ],
+  "description": "Optional: the tag this version gets when it goes live (a string = the tag name, such as 2026-10-28 / v2 final; or {name, title, note}). On a tagged page readers see the newest tagged version and can browse every tagged one (past issues); an existing tag name moves to this version. Daily reports use the day's date. Omitted: a page that has never been tagged behaves exactly as today; on a tagged page this version takes over the tag readers are looking at"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / note / description
      Added value: +"What changed this time: one line for subscribers and teammates, 20 characters or fewer, for example “Revised pricing after client feedback”. It appears in the update reminder; without it the reminder only says the version number, and the platform will not make one up."
    • addedInput schema / properties / quiet
      Added value: +{
+  "description": "true = no notification this time: when this version goes live, neither workspace people nor readers subscribed to this page are notified; subscribers are notified as usual on the next update. Use it for small edits such as typo fixes",
+  "type": "boolean"
+}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and non-idempotency; the description adds real context beyond them: 'Existing versions and comments remain', the explicit-approval gate, and the notification side effects of quiet=true, including that releasing a held version inherits the upload-time quiet choice. That is meaningful disclosure about side effects not encoded anywhere in the schema, though permissions and rollback reversibility are still unstated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core is front-loaded and each of the first four sentences carries real information about preconditions and notification effects. The trailing keyword list ('publish · web page · webpage · link · share · share to WeChat · ...') is thirteen tokens of search-style noise that add nothing to an agent's decision.

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 destructive, non-idempotent mutation with no output schema, the description covers the trigger condition, the survival of existing versions/comments, and the notification matrix. What is missing is modest: whether this requires a specific role or permission, and what happens to readers mid-session when the live version switches.

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 75% and tag/note/quiet are already richly documented there, so the description only needs to compensate at the margin. It does add one non-obvious interaction (quiet on a held version carries over from upload), but version_id — the sole required parameter — is undocumented in both schema and description beyond the vague 'roll back to an earlier approved version'.

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 first sentence states a specific verb and resource pair ('make an approved version live', 'roll back to an earlier approved version'), which is far more precise than the title alone. It doesn't explicitly distinguish itself from near siblings like publish_file, tag_version, or revoke_versions, so the agent still has to infer which switching tool applies.

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

Usage Guidelines4/5

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

It gives a hard precondition — 'Call only after the user explicitly approves publishing or rolling back' — plus the useful edge case that approved uploads without hold may already be live, avoiding a redundant call. It never names an alternative tool, so the routing guidance to siblings is implied rather than stated.

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

All LivePage · 活页 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources