Skip to main content
Glama

SnapHost

by ai.snaphost
OverviewDiscussionsAdmin

Get site content

get_site_content
Read-onlyIdempotent

Fetch a site's current entry document by id so you can edit it and push the result back with update_site: the read half of the round-trip get_site and list_sites omit (they return only metadata, never the body). Returns the live document inline as UTF-8 (encoding: "utf-8") for HTML/Markdown/text/SVG/JSON, or base64 (encoding: "base64") for binary content like PDFs and images, alongside content_type, content_kind, and content_hash. A site whose content_kind is not html was rendered from a file (Markdown, a notebook, a Word, PowerPoint or Excel file, a CSV, a PDF, an image, a video, an audio, a Mermaid diagram or a text file): what comes back is its rendered page, not the file, and the result says so in note. To change such a site, send a new file to update_site; sending edited HTML turns it into an HTML site. Pass original true to fetch the uploaded file itself when the page offers it for download (get_site reports original_included); refused when it does not.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_idYesThe id of the site whose content to fetch
originalNoFetch the uploaded file the page carries for download (a .pptx, an image, a CSV) instead of the rendered page
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
    • addedInput schema / properties / original
      Added value: +{
+  "description": "Fetch the uploaded file the page carries for download (a .pptx, an image, a CSV) instead of the rendered page",
+  "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.2/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), so the description's burden is lighter. It still adds real behavioral context beyond annotations: the encoding dual-mode (utf-8 vs base64 by content type), the rendered-vs-uploaded distinction for non-HTML sites, and the `note` field disclosure. It does not mention pagination or size limits, but the richer return-shape detail outweighs that gap.

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

Conciseness3/5

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

Front-loaded with the core action and sibling differentiation, which is good. However it is quite long and packed with clause-heavy sentences (encoding, content_kind, update_site round-trip, original). Every sentence carries information, but the density reduces scannability for an agent parsing quickly.

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?

The tool has no output schema, so the description must explain returns – it does so thoroughly (inline UTF-8 vs base64, content_type/content_kind/content_hash, note, original_included). An agent has what it needs to invoke and interpret the result. Minor gap: no mention of maximum content size or streaming.

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 the baseline is 3. The description does reinforce `original` (uploaded file vs rendered page) and the workspace write-context constraint, adding modest value, but the schema already documents all three parameters with descriptions.

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 (fetch) and resource (a site's current entry document by id), and explicitly distinguishes itself from siblings get_site and list_sites by noting 'the read half of the round-trip get_site and list_sites omit (they return only metadata, never the body).' An agent can route between these tools without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly frames its place in a workflow ('so you can edit it and push the result back with update_site') and describes the alternative path for non-HTML sites ('To change such a site, send a new file to update_site'). The `original` parameter's when-to-use condition is spelled out.

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