Skip to main content
Glama

Pagetool

Rename a site

rename_site
Idempotent

Changes a site's display name (shown in list_sites and the dashboard). Plain text; HTML entities like ' are decoded. Max 120 characters. Signed-in accounts only. Free.

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": "rename_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe new display name, plain text, e.g. "Pappy's Place". HTML entities are decoded. Max 120 characters. One of name / page_title is required; page_title alone retitles the home page without renaming the site.
stageNotrue = put the home page title change on the staged copy (publish_staged makes it live). The operator token always stages on a published site.
site_keyNoThe site to rename. Defaults to the caller's current draft site when omitted.
page_titleNoOptional browser-tab / search title for the home page (max 70 characters). Without it, a default home title such as "My Page" (or the old site name) is replaced by the new name; a custom title is kept.
og_image_urlNoOptional link-preview (share card) image for the home page: an https:// image URL, max 500 characters. Without it, the first image on the page is used.
page_descriptionNoOptional search-snippet and link-preview description for the home page, 1-300 characters. Write a sentence that makes sense on its own (it is shown out of context). Without it, the first text on the page is used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare a non-destructive, idempotent write, and the description adds genuinely new context: signed-in accounts only, no cost, plain-text handling with HTML entity decoding, and a 120-character cap. It stops short of saying whether the old name is recoverable or how the staged-vs-live path behaves, but that is a minor gap.

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?

Five short, front-loaded statements with no filler — purpose first, then constraints, then eligibility and cost. The telegraphic "Signed-in accounts only. Free." fragments are efficient rather than confusing.

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?

With six parameters fully documented in the schema and no output schema, the description covers the remaining burden: auth requirement, cost, input format, and length limit. It omits error/rollback behavior and how staging interacts with a rename, which keeps it from a 5.

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 explains every parameter in detail. The description reinforces the name parameter's plain-text/entity-decoding/120-character rules but adds no meaning beyond what the schema states; baseline 3 applies.

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

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Changes a site's display name") and clarifies scope with "shown in list_sites and the dashboard", which distinguishes the display name from other site attributes. It does not name any sibling tool it is not, so it falls short of full sibling differentiation.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance. The important distinction — that supplying page_title alone retitles the home page without renaming the site — appears only in the input schema, not in the description, so an agent skimming the description gets no routing help.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources