Skip to main content
Glama

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: after approval the version is NOT released until the user confirms the preview and you call publish_version. 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

TableJSON Schema
NameRequiredDescriptionDefault
holdNo默认 true：传完过审后先不切给客户看，确认后调 publish_version。false = 过审即自动发布
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 / 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."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations (readOnly=false, idempotent=false, destructive=false, openWorld=false) only cover the safety profile; the description adds substantial behavior: link valid 2 hours, succeeds only once, uploads into this one page only, no login required, hold defaults to true so release waits on publish_version, and the required polling loop via get_version with state semantics (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?

Front-loaded and informative, but the routing rule is stated twice (the 'no terminal / 2 MB' condition appears both in the routing list and again in the 'Use this when' sentence), and the post-call follow-up procedure is long. Content is useful but not tightly edited.

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?

With no output schema, the description compensates fully: it explains what is returned (a url plus a page-details link), how long it lives, what the agent must do with it (hand over unchanged, specify the file, wait for 'uploaded'), and the full polling/confirmation workflow through get_version and publish_version.

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 baseline is 3, but the description adds real semantics beyond the schema: proposal_id targets an existing page (find via list_proposals) and is mutually exclusive with title, title creates a new page, folder_id is optional, and hold=true blocks release until publish_version. Only the note parameter's role is left to the schema.

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?

States a specific verb+resource: creates an upload page link that the user opens to pick files (PDF/PPTX/images/large files). It explicitly names the siblings it is not (create_cli_token, publish_file) and the routing conditions, so an agent can distinguish it 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?

Gives an explicit decision tree: terminal ⇒ SPACE CLI (create_cli_token first); no terminal + text files ≤2 MB ⇒ publish_file; anything else or unsure ⇒ create_upload_link. Also names the alternative for single HTML/Markdown with content in hand (publish_file). When-to-use and when-not-to-use are both covered.

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