Skip to main content
Glama

SnapHost

by ai.snaphost
OverviewDiscussionsAdmin

List sites

list_sites
Read-onlyIdempotent

List the non-deleted sites in one workspace (the one named by workspace_id, the personal space when omitted; sites live in exactly one workspace) with their ids, slugs, titles, statuses, visibilities (public or allowlist, i.e. private), share URLs, detected content kind (content_kind), SPA fallback (spa_fallback), auto-refresh on update (auto_refresh), allowed external origins (external_origins), link expiry (link_expires_at, ISO or null) with its derived link_status (no_expiry, active, expiring_soon, or expired), and whether a view password is set (has_view_password). Narrow the results with the optional visibility, status, link_status, and expires_within_days filters; all combine with AND.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoOnly sites in this lifecycle state (`published` is live)
visibilityNoOnly sites with this visibility (`allowlist` is private/restricted)
link_statusNoOnly sites whose share link is in this expiry state
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).
expires_within_daysNoOnly sites whose link expires within this many days and has not lapsed

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

A3.9/5.0
Behavior4/5

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

Annotations already declare this is a safe, idempotent, read-only, closed-world operation. The description adds the non-deleted scoping constraint and the workspace-confinement rule ('sites live in exactly one workspace') which is not obvious from annotations. Doesn't cover pagination or result caps, but that's a modest gap given the safety profile is already covered.

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

Conciseness2/5

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

A single dense sentence crams the full field list, the field semantics parenthetical, and the filter semantics into one block. It is front-loaded correctly but overly packed – the enumerated return fields arguably belong in an output schema and make this hard to parse.

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 filter-list tool with full schema coverage and an existing annotations safety profile, the description covers workspace scoping, filter combination, and field inventory. No output schema exists, so enumerating return fields adds value, though pagination behavior remains unstated.

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%, so all five parameters are documented including enums for status, visibility, link_status. The description adds the AND-combination rule for filters and the workspace default behavior, but doesn't add syntax beyond what the schema provides. Baseline 3 for high-coverage 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?

Specific verb+resource with explicit scope: lists sites in a single named workspace, non-deleted only. Distinguishes from get_site (singular) and list_workspaces by stating exactly which entities are returned and the workspace scoping rule.

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?

Clear context: workspace_id is optional, defaults to personal space. Filter semantics are explained ('all combine with AND'). However, no explicit routing to alternatives among the many sibling list_* tools (list_workspaces, list_site_collections), leaving some inference to the agent.

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