Latchbell

Publish my full website

publish_website

Owners only (needs sign-in): Deploy the website: this is the step that makes the uploaded draft live at website_url. Publish only after the owner has seen the draft (preview_url in my_website) and said so; if they ask to deploy before seeing it, show them preview_url first. Runs the same page and browser checks as the dashboard and copies in any web images still on the draft. While the browser check is still running this answers publishing: true, and the site goes live by itself when the check passes. If it fails, or the draft changes first, nothing goes live, and my_website shows why.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "publish_website"
  }
}

Input Schema

Name	Required	Description	Default
`rev`	No	The rev the owner saw, so a draft that has changed since is not published

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing an ownership/sign-in requirement, an asynchronous response ('answers publishing: true' while the browser check runs), self-completion when the check passes, and fail-closed behavior where nothing goes live and my_website explains why. It also notes the side effect of copying in web images still on the draft.

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

Conciseness4/5

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

Front-loaded with the deployment effect and the ownership gate, then the safety precondition, then runtime behavior. It is dense and slightly overlong with several clauses packed into single sentences, but nearly every sentence carries distinct operational information.

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 single-optional-parameter mutation with no output schema, the description covers auth, prerequisites, async semantics, the exact return flag an agent will see, and failure handling. An agent could call this correctly and interpret the response without further context.

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% and the rev parameter is already documented, so the baseline is 3. The description earns an extra point by explaining the consequence of a stale rev: 'if it fails, or the draft changes first, nothing goes live,' which tells the agent why the parameter matters rather than just what it is.

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 and resource plus the concrete effect: 'Deploy the website: this is the step that makes the uploaded draft live at website_url.' The contrast with previewing (preview_url in my_website) makes the scope of 'website-wide' publication clear 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 precondition and a when-not path: publish only after the owner has seen the draft and said so, and if they ask to deploy earlier, show them preview_url first. That is a usable decision rule rather than a vague suggestion, and it also implies this is not the tool for draft review.

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

All Latchbell 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?