Skip to main content
Glama
Sign In

LivePage · 活页

by com.24haowan
OverviewDiscussionsAdmin

Send an upload page (the user uploads the files)

create_upload_link

Get an upload page for the user, who picks the files on their phone or computer (PDF / PPTX / images / large files). Which upload route: terminal ⇒ SPACE CLI (create_cli_token first); no terminal and text files up to 2 MB in total ⇒ publish_file; anything else or unsure ⇒ create_upload_link. Use this when you have NO terminal and the page is not text files within 2 MB (PDF, PPTX, images, large files), or when you are not sure: the platform creates an upload page link; give it to the user and they pick the files on their phone (WeChat works) or computer. The link is valid for 2 hours, succeeds only once, uploads only into this one page, and needs no login. To add a version to existing pages pass proposal_id (find it with list_proposals first); to create new pages pass title (optional folder_id). hold defaults to true: on a page others can already open, the approved version is NOT released until the user confirms the preview and you call publish_version; on a page only workspace members can open, it becomes current directly. After calling, hand the url to the user unchanged, say exactly which file to upload and ask them to come back and say “uploaded” when done; then call get_version with version_id every 15–30 seconds until it is no longer uploading: preview_ready or approved ⇒ give the user the preview URL to confirm; converting ⇒ keep polling; review ⇒ tell the user it is under manual review. After upload, the page also links to the page details for preview and sharing; keep following up through get_version and do not publish a version that is waiting to publish before the user confirms. For a single HTML or Markdown file whose content you already have, use publish_file instead — the user does not need to do anything. Keywords: publish · web page · webpage · link · share · share to WeChat · WeChat link · html · pdf · markdown · upload · LivePage · proposal.

Input Schema

NameRequiredDescriptionDefault
holdNo默认 true：传完过审后先不切给客户看，确认后调 publish_version。false = 过审即自动发布 Only takes effect once the page has readers outside the workspace (passcode, public, a folder link or a named link); on a page only workspace members can open it is ignored, and the approved version becomes current directly without notifying anyone.
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.
titleNo新建一份时的标题
folder_idNoOnly when creating a new page: destination folder; omit to keep it out of any folder.
proposal_idNo给已有页面传新版本时传；与 title 二选一

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / hold / description
      Previous value: -"默认 true：传完过审后先不切给客户看，确认后调 publish_version。false = 过审即自动发布"New value: +"默认 true：传完过审后先不切给客户看，确认后调 publish_version。false = 过审即自动发布 Only takes effect once the page has readers outside the workspace (passcode, public, a folder link or a named link); on a page only workspace members can open it is ignored, and the approved version becomes current directly without notifying anyone."
  2. Changed1 schema field changed
    • changedInput schema / properties / note / description
      Previous value: -"Version note, for example: V2, revised pricing after client feedback."New 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."
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say this is a non-read-only, non-destructive, non-idempotent call; the description adds far more: the link is valid 2 hours, succeeds only once, uploads only into that one page, needs no login, and works from WeChat. It also discloses the hold default and its conditional effect, and specifies the required post-call loop (hand the URL over unchanged, then poll get_version every 15–30s and branch on preview_ready/approved/converting/review).

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 routing rule is front-loaded and useful, but the decision tree is stated twice in near-identical wording, the hold explanation duplicates the schema text, and the trailing keywords block plus the throwaway line about the page linking to page details add length without adding decisions. The follow-up protocol is worth its words; the rest is padded.

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

Completeness5/5

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

For a five-parameter, zero-required tool with no output schema, the description covers everything an agent needs: selection, creation mode, the handoff instruction to the user, and the polling/confirmation loop through get_version up to publish_version. Nothing required to call it correctly or to finish the workflow is missing.

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 adds operational meaning beyond the schema: proposal_id and title are mutually exclusive modes (new version vs new page), folder_id only applies when creating, and proposal_id must be found via list_proposals first. It largely restates hold's semantics rather than extending them, which is why this is not a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 (create an upload page link the user opens to pick files) and explicitly separates it from the two plausible siblings, publish_file and create_cli_token. An agent can pick this tool without opening any schema.

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

Usage Guidelines5/5

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

It gives an explicit routing rule: terminal ⇒ SPACE CLI (create_cli_token first); no terminal plus text files under 2 MB total ⇒ publish_file; anything else or unsure ⇒ create_upload_link. It also names the alternative for a single HTML/Markdown file whose content the agent already has, which is a real exclusion, not just a suggestion.

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