Skip to main content
Glama

delivery_get

Read-only

Read one published item exactly as visitors see it from the Delivery API by path, documentId, slug, global, or start page. Returns URLs, SEO metadata, and no private fields, or null if no match.

Instructions

Read ONE item exactly as the website receives it from the public Delivery API — the way to check what visitors see. Name it by exactly one of: path (a page's URL, e.g. '/blog/my-post' — the usual choice), documentId, slug, global (a singleton's type, e.g. 'SiteHeader'), or start:true (the page served at /). Returns published content only (unless preview), private fields removed, plus computed urlPath, fieldTypes and SEO metadata on pages — or null when nothing matches. To read a draft for editing use get_content; for many items use delivery_list or delivery_search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoA page's URL path without the locale prefix, e.g. '/blog/my-post'.
siteNoSite slug or id to act in (multisite). Omit to use this server's default site. Call list_sites to see what exists — an empty tree or search usually means the wrong site, not missing content.
slugNoLast URL segment, e.g. 'about-us'. Unique only among siblings — prefer path.
startNotrue = the site's start page (set with set_start_page).
globalNoContent type of a global singleton (header, footer…), e.g. 'SiteHeader'. Find them with list_content {kind:'global'}.
localeNoLocale code. Omit for the document's own locale (its site-default variant, else its only variant).
previewNotrue = read the latest drafts as the preview pane shows them (needs site-wide read access). Default false: published content only, exactly what visitors get.
populateNoHow many levels of references and shared blocks to resolve inline, 0-4 (default 0: references stay as ids).
documentIdNoThe item's documentId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnlyHint/openWorldHint). The description adds genuinely new behavioral facts: published-only unless preview, private fields removed, computed urlPath/fieldTypes/SEO metadata on pages, null when nothing matches, and that preview requires site-wide read access. With no output schema, this return-behavior disclosure is high value.

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 purpose, then naming options, then return behavior, then routing to alternatives — a logical order with no filler sentences. It runs long (~110 words) and the parenthetical examples partly restate schema examples, but every clause carries usable information.

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 9-param, zero-required lookup tool with no output schema, the description covers the naming strategy, the published-vs-preview behavior, the null case, and the return shape. Remaining parameters (site, locale, populate) are fully documented in the schema, so nothing needed for a correct call is missing.

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?

Schema coverage is 100%, so the per-parameter docs already carry the baseline (3). The description adds real meaning beyond the schema: the mutual-exclusivity rule ('Name it by exactly one of ...') is not encoded as a oneOf constraint, and it flags path as 'the usual choice' and start:true as the root page. It does not add anything for site/locale/populate, but those are well documented in the 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?

States a specific verb+resource ('Read ONE item ... from the public Delivery API') and immediately frames the scope ('exactly as the website receives it ... what visitors see'). It explicitly distinguishes itself from siblings (get_content for drafts, delivery_list/search for many items), so an agent can select it without opening another 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?

Names the alternatives and the condition that selects each: 'To read a draft for editing use get_content; for many items use delivery_list or delivery_search.' It also gives positive guidance ('the way to check what visitors see') and the preview caveat, leaving nothing to inference.

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