Skip to main content
Glama
hybriden

Paperboy CMS

Official
by hybriden
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

delivery_list

Read-only

Fetch published content of one type for website listings, with pagination, sorting, and equality filters. Returns items and total.

Instructions

List the published content of one type as the website receives it (e.g. every BlogPost for a listing). Supports pagination (limit/offset), sorting and equality filters on data fields; without sort it follows the parent's declared child order. Private fields are removed. Returns { items, total }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
sortNoname | createdAt | data.<field>; prefix - for descending
typeYesContent type name, e.g. 'BlogPost'.
limitNoPage size, 1-500.
filterNoEquality filters on data fields, e.g. {"author": "Jane"}
localeNoLocale code. Omit for the document's own locale (its site-default variant, else its only variant).
offsetNoItems to skip, for paging.
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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.3
    • addedInput schema / properties / limit / description
      Added value: +"Page size, 1-500."
    • addedInput schema / properties / offset / description
      Added value: +"Items to skip, for paging."
    • addedInput schema / properties / populate / description
      Added value: +"How many levels of references and shared blocks to resolve inline, 0-4 (default 0: references stay as ids)."
    • changedInput schema / properties / preview / description
      Previous value: -"Use the preview perspective (drafts)"New value: +"true = read the latest drafts as the preview pane shows them (needs site-wide read access). Default false: published content only, exactly what visitors get."
    • addedInput schema / properties / type / description
      Added value: +"Content type name, e.g. 'BlogPost'."
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false; the description goes further by disclosing that private fields are stripped, that omitting sort falls back to the parent's declared child order, and that the response is { items, total }. It stops short of covering the preview/permission nuance (that lives in the schema) or any rate-limit/paging caveats.

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?

Two sentences, purpose front-loaded, and the final clause carries the return shape rather than padding. Dense but every clause carries information; only the parenthetical example borders on redundant.

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 nine parameters, no output schema, and nested filter objects, the description supplies the return shape, private-field removal, and default sort behavior an agent needs. It is thin on how populate/locale/preview interact, but those are reasonably covered in the schema itself.

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 baseline is 3, but the description adds semantics the schema does not: the default ordering when sort is absent, and the fact that filters apply to data fields specifically. This meaningfully supplements the parameter docs.

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 ('List the published content of one type') plus the delivery-side framing ('as the website receives it'), which cleanly separates it from the management-content siblings and from delivery_search/delivery_get_by_id. The BlogPost example makes the unit of return unambiguous.

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

Usage Guidelines3/5

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

The description implies when this tool applies (enumerating all items of one type for a listing) but never names an alternative such as delivery_search or get_content, nor states when-not to use it. Usage is inferable but not guided.

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

Deploy Server

Other Tools