Skip to main content
Glama
hybriden

Paperboy CMS

Official
by hybriden
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_webhook

Subscribe a public HTTPS URL to Paperboy CMS site events as admin; sends signed HMAC-SHA256 JSON POSTs for rebuilds and automations.

Instructions

Subscribe a URL to this site's events (Admin only): Paperboy POSTs a JSON payload signed with HMAC-SHA256 on each event, e.g. to trigger a static-site rebuild. Private-network URLs are refused. The signing secret is returned ONCE; store it to verify deliveries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPublic https:// endpoint to POST to.
nameYesLabel, e.g. 'Netlify rebuild'.
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.
eventsNoEvents to send: content.published, content.unpublished, form.submitted. Omit or [] for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.3
    • addedInput schema / properties / events / description
      Added value: +"Events to send: content.published, content.unpublished, form.submitted. Omit or [] for all."
    • addedInput schema / properties / name / description
      Added value: +"Label, e.g. 'Netlify rebuild'."
    • addedInput schema / properties / url / description
      Added value: +"Public https:// endpoint to POST to."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say this is a non-readOnly, non-idempotent write; the description adds substantive behavior: HMAC-SHA256 signed payloads, refusal of private-network URLs, admin-only access, and that the signing secret is returned exactly once. Those are operational facts an agent cannot get from the structured fields.

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?

Roughly 50 words in tightly packed sentences with the action first, the security caveat second, and the one-time-secret warning last. No filler clauses; every sentence carries a distinct fact.

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 covers the one return detail that matters (the secret is returned ONCE and must be stored), plus security constraints and permissions. Nothing needed to invoke this webhook-creation tool correctly is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so url/name/site/events are already documented in the schema; the description reinforces the public-endpoint and secret semantics but adds no parameter-level detail beyond it. Baseline 3 applies.

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 ('Subscribe a URL to this site's events') along with the mechanism (Paperboy POSTs a signed JSON payload), which clearly separates it from list_webhooks and delete_webhook siblings.

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 a concrete usage context ('to trigger a static-site rebuild') and a prerequisite ('Admin only'), so an agent knows the scenario and the permission bar. It stops short of naming alternatives such as list_webhooks or delete_webhook or stating when-not to use it.

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