Skip to main content
Glama
hybriden

Paperboy CMS

Official
by hybriden
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_delivery_key

Mint an admin-only Delivery API key for published content in site builds or draft content in previews; store the one-time secret immediately.

Instructions

Mint a Delivery API key for this site (Admin only). A public key reads published content only — safe for a website build; a preview key also reads drafts, so keep it server-side. The secret is returned ONCE in this response; store it now.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesLabel for where it is used, e.g. 'Astro site production'.
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.
typeYespublic = published only; preview = drafts too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.3
    • addedInput schema / properties / name / description
      Added value: +"Label for where it is used, e.g. 'Astro site production'."
    • addedInput schema / properties / type / description
      Added value: +"public = published only; preview = drafts too."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare the mutation profile (readOnly=false, idempotent=false, destructive=false). The description adds genuinely non-obvious behavior: the secret is returned exactly once and must be stored immediately, the admin-only restriction, and the security consequence of preview keys reading drafts.

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?

Three sentences, front-loaded with the action and permission, then the type trade-off, then the one-time-secret warning. No filler and the most failure-prone detail (store the secret now) is last and emphatic.

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, and the description compensates by explaining the return (the secret, shown once). For a 3-parameter mutation tool it covers permission, parameter choice, and the irreversible consequence.

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. The description still adds meaning for the type parameter beyond the enum text by framing public as safe for a public build and preview as server-side-only, and it contextualizes the site parameter's multisite fallback behavior.

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?

Specific verb (Mint) plus resource (Delivery API key) plus scope (this site) and permission gate (Admin only). It is trivially distinguishable from its siblings list_delivery_keys, revoke_delivery_key and rename_delivery_key.

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

Usage Guidelines4/5

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

Gives the decision rule for the two key types — public for a website build, preview when drafts are needed — plus the admin-only prerequisite and the security caveat for preview keys. It stops short of explicitly naming when not to use it or pointing at sibling tools like revoke_delivery_key.

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