Skip to main content
Glama
Sign In

Replo

by io.github.replohq
OverviewDiscussionsAdmin

Update site

update_site
DestructiveIdempotent

Rename a Replo site's dashboard display name. This does not change its SEO page title, which lives in the site's layout metadata, or its published page content. Use list_sites to find site IDs.

Input Schema

NameRequiredDescriptionDefault
nameYesThe new human-readable display name for the site. This is the site's name shown in the dashboard, distinct from the SEO page title in the site's layout metadata.
siteIdYesThe ID of the site to rename. Use list_sites to find site IDs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / siteId / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. Changed5 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / description
      Added value: +"McpUpdateSiteInput"
    • addedInput schema / properties / name / description
      Added value: +"The new human-readable display name for the site. This is the site's name shown in the dashboard, distinct from the SEO page title in the site's layout metadata."
    • addedInput schema / properties / siteId / description
      Added value: +"The ID of the site to rename. Use list_sites to find site IDs."
    • changedInput schema / required
      Previous value: -[
-  "siteId"
-]New value: +[
+  "siteId",
+  "name"
+]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true. The description adds genuinely useful scope disclosure by asserting that adjacent fields (SEO title, published content) are untouched, which softens the destructive flag's ambiguity for a rename. It does not explain permissions, reversibility, or the response, keeping it below a 5.

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?

Three tight sentences, front-loaded with the action and immediately followed by the disambiguation and the ID-lookup hint. No filler or redundancy.

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 two-parameter mutation with annotations and no output schema, the description covers what changes, what does not, and how to obtain the required siteId. Only minor gaps remain, such as whether the call fails on duplicate names or what a successful response looks like.

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 coverage is 100% and both parameters carry descriptions including the list_sites hint, so the description's 'Use list_sites to find site IDs' largely restates the schema. No additional semantics (format, constraints, edge cases like name collisions) are contributed beyond the structured fields, so baseline 3 applies.

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 precisely scoped resource: 'Rename a Replo site's dashboard display name.' It also carves out what this is not (SEO page title, published page content), which separates it from update_site_metadata and edit_site_page without the agent needing to open those schemas.

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?

'Use list_sites to find site IDs' gives a concrete prerequisite step and names the right sibling for discovery. The negation of SEO title/content implicitly routes metadata edits elsewhere, but it never explicitly names update_site_metadata as the alternative, so it falls short of a full when/when-not rubric.

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

All Replo 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