Skip to main content
Glama

SnapHost

by ai.snaphost
OverviewDiscussionsAdmin

Move site to folder

move_site_to_folder
Idempotent

File a site into a folder, keeping its share link. Pass the destination folder_id from list_folders; omit folder_id to move the site back to the drive root. Moving a site between a personal and a shared (workspace-wide) folder reconciles who can see it. Only the site’s creator can move it. Returns the updated site read model with its new folder_id. In the website workspace the Shared-drive marketing folder is served publicly at snaphost.ai/lp/ (a site filed one folder deeper at /lp//), so filing a site there makes it a landing page and moving a landing page CHANGES its /lp address; the result reports the new one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spaceNoDrive to use when moving to the root (no folder_id): `personal` (default) or `shared` (Pro workspaces only). Ignored when a folder_id is given.
site_idYesThe id of the site to file
folder_idNoThe destination folder id from list_folders. Omit to move the site to the drive root.
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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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)."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description adds significant behavior beyond annotations: share links are preserved, personal/shared moves change visibility, only the creator can move, and the public /lp URL can change for landing pages. None of this contradicts the readOnly/destructive/idempotent hints.

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?

Every sentence earns its place: purpose, usage, visibility effect, permission, return value, and the URL caveat. It is front-loaded and dense without being padded.

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 mutating tool with no output schema, it explains the return value, the permission precondition, the behavioral consequences, and the folder_id sourcing. The complex landing-page URL implication is explicitly called out, leaving no critical gap.

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?

The schema already documents every parameter in detail (100% coverage), so the baseline is 3. The description adds operational meaning for folder_id (source list_folders, omission equals root) and contextual semantics for personal vs shared moves, warranting a 4.

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 opens with 'File a site into a folder, keeping its share link', naming a specific verb, resource, and effect. It also clarifies the no-folder case (drive root) and distinguishes site filing from sibling folder operations such as move_folder.

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?

It gives clear operational guidance: fetch folder_id from list_folders, omit folder_id to move to root, and notes the creator-only restriction. There is no explicit when-not-to-use or alternative-tool comparison, so it stops short of a 5.

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