Paperboy CMS

Official

Overview Schema Source Related Servers Discussions Admin

list_content

Read-only

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.

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. kind 'trash': items removed with trash_content (any kind), newest first, with deletedAt; nothing is purged automatically, and restore_content brings one back. Everything comes back in one call (no paging). Edit any of them with get_content/update_content on its documentId. Requires the content.read permission (Admin, Editor, Author, Viewer — an Author only within their own sections).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>"
    },
    "name": "list_content"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	Yes	Which kind of content to list: page, block, global, or trash (what trash_content removed).
`site`	No	Site 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.

Changed2 schema fields changedv0.1.7Oct 21, 2026

changedInput schema / properties / kind / description

Previous value: -"Which kind of content to list."New value: +"Which kind of content to list: page, block, global, or trash (what trash_content removed)."

changedInput schema / properties / kind / enum

Previous value: -[
-  "page",
-  "block",
-  "global"
-]New value: +[
+  "page",
+  "block",
+  "global",
+  "trash"
+]

Addedv0.1.4Oct 21, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnlyHint), but the description adds real behavioral context: the required content.read permission with per-role caveats (an Author only within their own sections), the no-paging guarantee ('Everything comes back in one call'), the fact that nothing is purged automatically, and the shared-vs-inline block distinction that affects blast radius of edits. This is well beyond what the annotations declare.

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 core action and return shape before the per-kind detail, and every clause carries information. It is dense and slightly long, with some parenthetical enumeration that could be trimmed, but there is no filler or repetition.

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, so the description carries the return contract itself, naming the fields returned (documentId, name, type, per-locale status, parentId, folderId, deletedAt) plus ordering. Combined with the permission and paging disclosures, an agent has everything needed to call it correctly and interpret the result.

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?

Schema coverage is already 100%, so baseline would be 3, but the description meaningfully enriches both parameters: it defines what each kind actually contains, notes that trash items carry deletedAt and are newest-first, and explains the 'site' parameter's failure mode ('an empty tree or search usually means the wrong site, not missing content').

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 EVERY item of one kind in this site') and immediately scopes it as one flat array, distinguishing it from the tree-walking alternative by name. An agent can tell it apart from list_tree and get_content without opening a 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 when-to-use guidance per enum value: 'page' to find one by name or pick a parent, 'block' for shared reusable blocks, 'global' because it is the only way to enumerate singletons, 'trash' for removed items. It names the alternative (list_tree shows one level in display order) and the follow-up tools (get_content/update_content, restore_content), 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.