Skip to main content
Glama

Sitelas

by com.sitelas
OverviewDiscussionsAdmin

Read a page

get_page
Read-onlyIdempotent

Read what is on the site's DRAFT. view 'content' (default) lists every editable node id with its text, plus form fields, FAQ items, image nodes and collection items — call it when you come back to a site and before patch_nodes. view 'structure' gives the container nesting with ids (for moving, inserting or removing containers, and the only way to see how header/footer nodes nest). view 'copy' lists all rewriteable copy on the whole site for a full rewrite. To check what visitors see, use read_rendered_page; for pages, theme and publish state, get_site. Read-only.

Input Schema

NameRequiredDescriptionDefault
viewNo'content' (default): every patchable node id with its current text, each form's full field list, copy kept in node data (FAQ items, banner links, form messages), image nodes, slots, and each collection's items read live — the view to build a patch_nodes call from. 'structure': the container nesting with ids, types and short labels and no props — for moving, inserting into or removing a container; pass page_slug 'header' / 'footer' / 'pageLayout' / 'shell' for the shared chrome, or 'collection:<contentType>' for a collection's detail template. 'copy': every rewriteable text field on the WHOLE site, chrome and collection items included, for a full copy pass.
site_idYes
max_itemsNoWith view 'copy': cap on returned items (default 200). When `truncated` is true, or content_items_returned is below content_items_total, call again with a higher cap before reporting the pass done.
page_slugNoWhich page, e.g. '/', '/about'. 'content': omit for the whole site (large — scope it when editing one page; the header, footer and collections are always included, in site_elements, so 'header' or 'footer' returns the home page with them). 'structure': defaults to the home page. Ignored by 'copy'.
instructionsNoWith view 'copy': the rewrite intent ('more formal', 'shorter'), echoed back. Nothing is rewritten for you — compose the new copy and apply it with patch_nodes / edit_content_item.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly annotation by disclosing that this reads the DRAFT not the live site, that whole-site content views are large and should be scoped, that header/footer/collections are always included in site_elements, and that copy view rewrites nothing for the agent.

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-loads the draft-vs-live distinction and then routes by view in one dense paragraph; only the trailing 'Read-only.' is redundant with annotations, otherwise there is little waste.

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?

No output schema exists, yet the description explains what each view returns (node ids with text, form fields, FAQ items, container nesting, site-wide copy) and the max_items/truncated retry behavior, which is enough to call it correctly.

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 80% and the schema's own param descriptions are richer than the prose (e.g. view enums, page_slug caveats, max_items truncation follow-up are all repeated in schema). The description adds selection guidance for views but little parameter meaning the schema lacks.

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 ('Read what is on the site's DRAFT') and immediately distinguishes the three output modes, so an agent knows exactly what it returns versus read_rendered_page or get_site.

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?

Explicit routing: 'content' is for returning to a site and before patch_nodes, 'structure' for moving/inserting/removing containers, 'copy' for a full rewrite, plus named alternatives (read_rendered_page for visitor view, get_site for pages/theme/publish state).

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