Skip to main content
Glama
hybriden

Paperboy CMS

Official
by hybriden
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_content

Read-only

Enumerate all pages, shared blocks, or global singletons in a Paperboy CMS site as a flat array with IDs, names, types, statuses, and parent/folder links for quick lookup and editing.

Instructions

List EVERY item of one kind in this site that you can see, as one flat array (documentId, name, type, per-locale status, plus parentId for pages and folderId for blocks) — no tree walking needed. kind 'page': pages, to find one by name or pick a parent/reference target (list_tree shows one level in display order). kind 'block': SHARED blocks — reusable block documents (banners, forms, CTAs…) that pages place by reference, so one edit updates every page using them; inline blocks live inside a page's data and are not listed. kind 'global': singletons (header, footer, site settings…), which are neither in the page tree nor blocks, so this is the only way to enumerate them. Edit any of them with get_content/update_content on its documentId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYesWhich kind of content to list.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A5/5.0
Behavior5/5

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

Beyond the `readOnlyHint` annotation, the description meticulously details the result set's behavior. It clarifies that 'inline blocks live inside a page's data and are not listed' and specifies the exact fields included in the flat array, offering critical constraints on the output structure.

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

Conciseness5/5

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

The description is densely packed but highly efficient. It front-loads the core purpose and then organizes the remaining text into logical, defining chunks based on the content 'kind' (page, block, global), ensuring every sentence clarifies scope or usage.

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?

Given that no output schema exists, the definition is exceptionally complete. It specifies the exact attributes returned (documentId, name, type, etc.) and addresses complex structural edge cases, such as why inline blocks are excluded from the listing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While schema coverage is 100%, the description adds immense semantic value by defining the functional meaning of the `kind` enum. For example, it explains that `block` content is 'SHARED blocks — reusable block documents' and that `global` content is necessary 'to enumerate them' as singletons.

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?

The purpose is stated immediately: to list 'EVERY item of one kind in this site.' It distinguishes itself by specifying the output format—a 'flat array'—and defining the scope of the three content kinds: page, block, and global.

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?

It provides detailed instructions on when to use this tool by contrasting it with sibling tools, noting that 'no tree walking needed,' unlike what `list_tree` performs. It also clarifies the relationship between the content kinds, such as how `block` documents are reusable and how `global` content must be used for singletons.

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