Skip to main content
Glama
Sign In
Postbuild MCP

Postbuild MCP

Official
by xdlabs-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Sync Multi-Site Readiness Telemetry to LAUNCH_STATUS.md or Obsidian VaultOS

postbuild_vault_sync
Idempotent

Audit multiple project URLs over HTTPS and persist a consolidated Markdown launch dashboard plus JSON telemetry to a repository or Obsidian vault for ongoing readiness tracking.

Instructions

Audit every URL in urls over HTTPS and write a consolidated Markdown readiness dashboard plus JSON telemetry cache into vault_path. When vault_path contains an .obsidian/ directory, writes _dashboards/Postbuild Launch.md and _meta/postbuild-telemetry.json for Obsidian VaultOS; otherwise writes LAUNCH_STATUS.md and .postbuild/telemetry.json at the root of vault_path (when urls is omitted, audits the domain bound to the active pb_live_... Launch Pass license; overwrites only those generated status/telemetry files and never alters user notes). Use this tool to persist multi-project launch telemetry to a repository or Obsidian vault; do not use it for a single-URL in-memory JSON audit (postbuild_scan) or to generate robots.txt/sitemap.xml/llms.txt (postbuild_fix).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "postbuild_vault_sync"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsNoPublic HTTP/HTTPS project URLs to audit and aggregate into the synced dashboard (defaults to the licensed domain).
vault_pathNoLocal repository root or Obsidian vault directory where status Markdown and telemetry JSON are written (defaults to `process.cwd()`).

Output Schema

NameRequiredDescriptionDefault
okYesTrue when all target URLs were audited and dashboard/telemetry files were written.
modeYesOutput layout selected based on whether `.obsidian/` exists in `vault_path`.
vaultPathYesResolved absolute path of `vault_path`.
dashboardPathYesAbsolute path to the written Markdown dashboard (`LAUNCH_STATUS.md` or `_dashboards/Postbuild Launch.md`).
telemetryPathYesAbsolute path to the written JSON telemetry cache (`.postbuild/telemetry.json` or `_meta/postbuild-telemetry.json`).
syncedProjectsYesNumber of project URLs audited and written to the dashboard.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.24
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / urls / description
      Previous value: -"List of project URLs to audit and sync"New value: +"Public HTTP/HTTPS project URLs to audit and aggregate into the synced dashboard (defaults to the licensed domain)."
    • changedInput schema / properties / vault_path / description
      Previous value: -"Target repository or Obsidian vault path (defaults to current working directory)"New value: +"Local repository root or Obsidian vault directory where status Markdown and telemetry JSON are written (defaults to `process.cwd()`)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "dashboardPath": {
+      "description": "Absolute path to the written Markdown dashboard (`LAUNCH_STATUS.md` or `_dashboards/Postbuild Launch.md`).",
+      "type": "string"
+    },
+    "mode": {
+      "description": "Output layout selected based on whether `.obsidian/` exists in `vault_path`.",
+      "enum": [
+        "obsidian_vault",
+        "repo_markdown"
+      ],
+      "type": "string"
+    },
+    "ok": {
+      "description": "True when all target URLs were audited and dashboard/telemetry files were written.",
+      "type": "boolean"
+    },
+    "syncedProjects": {
+      "description": "Number of project URLs audited and written to the dashboard.",
+      "type": "number"
+    },
+    "telemetryPath": {
+      "description": "Absolute path to the written JSON telemetry cache (`.postbuild/telemetry.json` or `_meta/postbuild-telemetry.json`).",
+      "type": "string"
+    },
+    "vaultPath": {
+      "description": "Resolved absolute path of `vault_path`.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "mode",
+    "vaultPath",
+    "dashboardPath",
+    "telemetryPath",
+    "syncedProjects"
+  ],
+  "type": "object"
+}
  2. First observedv2.1.23

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description adds the crucial scope detail: only the generated status/telemetry files are overwritten and user notes are never altered. It also discloses the license-bound default domain and the `.obsidian/` detection branch. It stops short of describing failure handling for unreachable URLs or the size/shape of the written artifacts.

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, then the conditional output layout, then the routing guidance, so an agent can stop reading once it has what it needs. The single long parenthetical sentence is dense but every clause carries operational information.

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?

With an output schema present, return values need no explanation; the remaining gaps an agent would care about — where files land, what is overwritten, and what happens when `urls` is omitted — are all covered. Complete for a two-parameter write tool.

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 already 100%, so the baseline is 3; the description still earns above that by explaining the branch semantics of `vault_path` (which output paths appear depending on `.obsidian/` presence) and the license-derived default for `urls`. This is meaning the schema alone does not convey.

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 concrete compound action (audit URLs over HTTPS, then write a Markdown dashboard plus JSON telemetry) and names the exact artifacts produced. It also distinguishes itself from postbuild_scan and postbuild_fix by describing what those tools do instead.

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?

Explicitly gives the when ('persist multi-project launch telemetry to a repository or Obsidian vault') and the when-not, naming both alternatives and the conditions that select them (single-URL in-memory audit, artifact generation). Nothing is left to inference.

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