qr-maker

update_landing

Modify HTML content and title of a published landing page while preserving its existing short link and QR code functionality.

Instructions

Update a landing page HTML content and re-publish to CDN. The existing short link and QR code continue to work — only the page content changes.

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": {
      "landing_id": "<landing_id>",
      "html": "<html>"
    },
    "name": "update_landing"
  }
}

Input Schema

Name	Required	Description
`landing_id`	Yes	The landing page ID to update
`html`	Yes	New HTML content for the landing page
`title`	No	Optional new title

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: it's a mutation operation ('update'), it triggers a CDN re-publish, and it preserves existing short links and QR codes. It lacks details on permissions, rate limits, or error handling, but covers essential operational context.

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 front-loaded with the core purpose in the first sentence, followed by an important behavioral detail. Both sentences are essential—no wasted words—making it highly efficient and well-structured.

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 mutation tool with no annotations and no output schema, the description does a good job covering purpose, behavior, and context. It could be more complete by addressing potential side effects or response format, but it provides sufficient guidance for basic use given the tool's complexity.

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%, so the schema already documents all parameters. The description adds no additional parameter-specific information beyond what the schema provides, such as formatting details or constraints. This meets the baseline for high schema coverage.

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 clearly states the specific action ('update a landing page HTML content and re-publish to CDN'), identifies the resource ('landing page'), and distinguishes it from siblings like 'publish_landing' by specifying that only content changes while short links and QR codes remain functional.

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?

The description provides clear context for when to use this tool ('update a landing page HTML content') and implicitly differentiates it from 'publish_landing' by noting that existing short links and QR codes continue to work. However, it does not explicitly state when not to use it or mention alternatives like 'update_template'.

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