Skip to main content
Glama

SnapHost

by ai.snaphost
OverviewDiscussionsAdmin

Set collection access

set_collection_access
Idempotent

Set who can read a collection from the published page and pause/resume writes. access_mode: 'public_read' (anyone reads: a scoreboard/guestbook) or 'append_only' (visitors append but only the owner reads: a contact form / waitlist; submissions are never readable by other visitors). On the marketing site public_read means anyone on the internet, so it is refused unless you pass records_carry_no_personal_detail true, which you answer with the owner, and the waitlist collection stays append_only there whatever is asked. writes_paused stops new appends. Needs Pro; scoped to a site you own.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_idYesThe site that owns the collection
collectionYesThe collection name
access_modeNo'append_only' for forms/waitlists; 'public_read' for shared lists
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).
writes_pausedNoPause (true) or resume (false) appends
records_carry_no_personal_detailNoRequired to set public_read on the marketing site: confirm with the owner, in words, that these records carry no name, email or other personal detail, because public_read there means anyone on the internet can read every one of them.

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.8/5.0
Behavior5/5

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

Beyond the annotations, it discloses ownership and plan requirements ('Needs Pro; scoped to a site you own'), the refusal behavior when records_carry_no_personal_detail is false, and the override where waitlist remains append_only. This is valuable behavioral context that annotations alone do not provide.

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?

The description is compact and front-loaded: the purpose in the first sentence, then mode semantics, then caveats. Every sentence earns its place and no repeated schema boilerplate appears.

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 access-control tool with no output schema, it provides everything needed to call correctly: modes, use cases, constraints, requirements, and exception behavior. The optional workspace_id detail remains in the schema, so nothing essential is missing from the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Because schema coverage is 100%, a baseline of 3 applies, but the description goes well beyond it: it explains the access_mode enum with use cases, defines the privacy implication of append_only, and clarifies the sensitive records_carry_no_personal_detail parameter and its owner-confirmation requirement.

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 a specific verb and resource: 'Set who can read a collection from the published page and pause/resume writes.' It then defines the two access modes with concrete examples, making the tool's scope distinct from sibling setters like set_visibility or set_site_data.

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 context for when each access_mode is appropriate (scoreboard/guestbook vs contact form/waitlist) and states hard constraints: public_read is refused on the marketing site without confirmation, and waitlist stays append_only. It doesn't explicitly name alternatives among sibling tools, but the use-case guidance is sufficient for selection.

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