Skip to main content
Glama
Sign In

SnapHost

by ai.snaphost
OverviewDiscussionsAdmin

Set site slug

set_site_slug
Idempotent

Change a site's slug, the last segment of its address on the workspace host and, for a landing page, of its snaphost.ai/lp address. The share permalink (nanoId) keeps working, and the old address on the workspace host forwards to the new one until another site takes it or remove_site_forward stops it; an /lp address and any campaign link to it stop. Normalised to lowercase letters, digits and hyphens; refused when another site on the same drive holds it, and when the new address is an old one still forwarding to another site: ask the user, then retry with replace_forward to stop that forward. Needs a workspace on Pro, which publishes on its own host.

Input Schema

NameRequiredDescriptionDefault
slugYesThe new slug
site_idYesThe id of the site
workspace_idNoOptional: the workspace to act in, from list_workspaces (the connection reaches the person's personal space and every workspace they are a member of). Required on a write when the connection reaches more than one workspace. Omit to act in the personal space (for an older single-workspace connection, the one workspace it was authorized for).
replace_forwardNoTake the address even though it forwards to another site, stopping that forward. Only after the user agreed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / replace_forward
      Added value: +{
+  "description": "Take the address even though it forwards to another site, stopping that forward. Only after the user agreed.",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / workspace_id / description
      Previous value: -"Optional: the workspace (the personal space or a Pro workspace) to act in, from list_workspaces. Omit to act in the token owner's own account."New value: +"Optional: the workspace to act in, from list_workspaces (the connection reaches the person's personal space and every workspace they are a member of). Required on a write when the connection reaches more than one workspace. Omit to act in the personal space (for an older single-workspace connection, the one workspace it was authorized for)."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations (readOnly=false, idempotent=true, destructive=false) by disclosing that the nanoId permalink survives, the old workspace-host address forwards, and that /lp addresses and campaign links to them break. It also documents normalisation rules, the conflict-refusal path, and the plan requirement. Minor tension with destructiveHint=false exists since lp/campaign links stop resolving, but that is an expected consequence of a rename rather than data destruction.

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 core action and its definition, and every clause carries information (forwarding, breakage, normalisation, refusals, plan). The single dense paragraph is long and clause-heavy, which slightly hurts scanability, but nothing is filler.

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 mutation tool with no output schema, the definition covers the side effects, conflict handling, retry path, workspace_id scoping, and plan prerequisite an agent needs to call it safely. Nothing material is left unspecified.

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%, so the baseline is 3, but the description adds operational meaning beyond the schema: replace_forward is framed as 'stop that forward' only after user agreement, and slug is characterised by its normalised character set and collision refusal. Useful augmentation on top of an already documented schema.

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 ('Change a site's slug') and immediately defines the slug as 'the last segment of its address on the workspace host', which implicitly separates it from rename_site and set_folder_slug. An agent can identify the operation and its scope without opening the schema.

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?

Gives clear conditional guidance: ask the user then retry with replace_forward when the address is still forwarding, and notes the Pro-workspace prerequisite. It stops short of explicitly contrasting with sibling tools (rename_site, update_site, set_folder_slug) or stating when a slug change is inappropriate.

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

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