Skip to main content
Glama

Sitelas

by com.sitelas
OverviewDiscussionsAdmin

Read the rendered page

read_rendered_page
Read-onlyIdempotent

THE DEFAULT WAY TO CHECK YOUR WORK. Fetch a page's SERVER-RENDERED text via the preview URL — the visible copy, headings, and (for collection/list pages) the expanded items — in ~35ms with no browser. Call it on every page you touched, before showing the user anything. It is what catches the failure you cannot otherwise see: template copy that survived your edit. A consultant template's funding-stage dropdown on a bike shop, a US Medicare FAQ on a UK dental practice — both shipped because nobody read the page back, and neither looks like an error in a diff. Prefer this over screenshot_page, which runs a real browser, takes ~40x longer, and answers a different question (how it LOOKS, not what it SAYS). Read-side pair to get_page (with view: "structure"): that shows STRUCTURE, this shows RENDERED CONTENT. Reads the draft via the preview URL. Read-only. live: true checks the published site instead (and its dead links); item renders one collection item's draft.

Input Schema

NameRequiredDescriptionDefault
itemNoRender one collection item's DRAFT through its detail template, without publishing: its text, links and problems such as unresolved {{placeholders}}. Use it right after add_content_item or a detail-template edit.
liveNoCheck the LIVE site instead: that it is published and renders, and which internal links point at pages that do not exist (`dead_links` — fix those before telling the owner it is ready). Use it after publishing, before sharing the address.
slugNoPage slug to read (e.g. '/' or '/blog' or '/blog/my-post'). Defaults to '/'.
site_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds substantive behavior: server-side render in ~35ms with no browser, reads the draft via preview URL, live mode also surfaces dead links. It also explains what it catches that a diff cannot — exactly the context an agent needs to trust the result.

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 primary directive and the key contrast, but the bike-shop and Medicare FAQ anecdotes, while persuasive, add length that a schema-driven reader does not strictly need. Efficient overall, slightly padded by narrative.

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?

With no output schema, the description does describe the return shape (rendered text, headings, expanded items, `dead_links`) and the two modes. Missing only explicit pagination/size limits for very large pages, which is minor for a read tool.

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 `live`, `item`, and `slug` parameters are all given purpose and timing in the description, well beyond the schema's own text. `site_id` is left undocumented in both places, but the remaining semantics are strong enough to exceed the 75%-coverage baseline.

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 ('Fetch a page's SERVER-RENDERED text via the preview URL') and enumerates what comes back (visible copy, headings, expanded list items). It explicitly separates itself from get_page (structure) and screenshot_page (looks), so an agent can pick it without opening any schema.

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?

Gives explicit triggers: 'Call it on every page you touched, before showing the user anything', prefer over screenshot_page, `live: true` after publishing and before sharing the address, `item` right after add_content_item or a detail-template edit. Alternatives and exclusions are named outright.

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

All Sitelas toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources