QRStuff MCP Server

Update link page

update_link_page

DestructiveIdempotent

Use this when the user wants to rename a landing page or publish or unpublish it (status draft or published). Publishing makes it public. It does not edit page content; for that give the user the editor link from get_link_page.

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": {
      "page_id": "<page_id>"
    },
    "name": "update_link_page"
  }
}

Input Schema

Name	Required	Description
`title`	No	New page title. Leave empty to keep the current one.
`status`	No	draft or published. Publishing makes the page public.
`page_id`	Yes	Landing page ID from `list_link_pages`. Never guess an ID.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructive, idempotent, and openWorld behavior. The description adds the material consequence that publishing makes the page public and clarifies it does not edit content, but it does not explain other destructive implications (e.g., unpublishing affecting live links) or permission/auth needs.

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?

Two sentences, front-loaded with the trigger and scope, with no wasted text. The content-edit exclusion is placed where it prevents misuse.

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?

The output schema covers return values and annotations cover safety semantics, so the description only needs to cover action, side effects, and routing. It does most of that well, missing only minor operational details like permissions or effects on existing published links.

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 100%, and the schema already documents title, status, and page_id. The description reinforces the status values and public effect but adds little syntax or meaning beyond what the schema provides.

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 specific actions (rename, publish/unpublish) and resource (landing page), and explicitly scopes out content editing. An agent can distinguish it from get_link_page and from content-editing operations, though it does not name every sibling such as update_short_link.

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 a direct trigger ('Use this when the user wants to rename... or publish or unpublish') and an explicit exclusion with the alternative get_link_page for page-content edits. Covers both when to use and one key when-not/alternative.

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

All QRStuff MCP Server tools Inspect

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

Need Help?