multisite-cms-mcp 1.2.4 → 1.4.0

package/dist/tools/get-schema.js

@@ -2,325 +2,141 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.getSchema = getSchema;
 /**
- * Returns the complete CMS schema with all built-in and custom collections
+ * Returns the complete CMS schema reference for custom collections
  */
 async function getSchema() {
     return `# CMS Schema Reference
 
-## Built-in Collections
-
-### Blog Posts (\`blogs\`)
-Time-stamped articles with optional author reference.
-
-**Fields:**
-- \`{{name}}\` (text, required) - Post title
-- \`{{slug}}\` (text, required) - URL slug
-- \`{{mainImage}}\` (image) - Hero/cover image URL
-- \`{{thumbnailImage}}\` (image) - Smaller preview image
-- \`{{postSummary}}\` (text) - Short excerpt/description
-- \`{{{postBody}}}\` (richText) - Main content (MUST use triple braces)
-- \`{{featured}}\` (boolean) - Featured flag
-- \`{{url}}\` (special) - Generated URL to post detail page
-
-**Date tokens (automatically tracked):**
-- \`{{createdAt}}\` - When the post was first created
-- \`{{publishedAt}}\` - When the post was published (empty for drafts)
-- \`{{updatedAt}}\` - When the post was last updated
-
-**Author Reference (when assigned):**
-- \`{{author.name}}\` - Author's name
-- \`{{author.picture}}\` - Author's photo URL
-- \`{{{author.bio}}}\` (richText) - Author's biography
-- \`{{author.email}}\` - Author's email
-- \`{{author.twitterProfileLink}}\` - Twitter URL
-- \`{{author.linkedinProfileLink}}\` - LinkedIn URL
-- \`{{author.url}}\` - Link to author's page
-
-**Loop syntax:** \`{{#each blogs}}\` or \`{{#each blogs featured=true limit=3}}\`
+## Collections Overview
 
----
-
-### Authors (\`authors\`)
-Content creators who can be referenced by blog posts.
-
-**Fields:**
-- \`{{name}}\` (text, required) - Author's name
-- \`{{slug}}\` (text, required) - URL slug
-- \`{{{bio}}}\` (richText) - Biography (MUST use triple braces)
-- \`{{picture}}\` (image) - Author photo URL
-- \`{{email}}\` (email) - Email address
-- \`{{twitterProfileLink}}\` (url) - Twitter URL
-- \`{{linkedinProfileLink}}\` (url) - LinkedIn URL
-- \`{{url}}\` (special) - Generated URL to author detail page
+All CMS content is managed through **custom collections**. Collections are content types you define (e.g., Blog Posts, Team Members, Services, Products) with custom fields.
 
-**Loop syntax:** \`{{#each authors}}\`
+**To see the exact collections and fields for a specific project, use the \`get_tenant_schema\` tool.**
 
 ---
 
-### Team Members (\`team\`)
-Staff, employees, leadership profiles.
+## Collection Templates
 
-**Fields:**
-- \`{{name}}\` (text, required) - Team member's name
-- \`{{slug}}\` (text) - URL slug (if using detail pages)
-- \`{{role}}\` (text) - Job title/role
-- \`{{{bio}}}\` (richText) - Biography (MUST use triple braces)
-- \`{{photo}}\` (image) - Headshot/photo URL
-- \`{{email}}\` (email) - Email address
-- \`{{order}}\` (number) - Display order
-
-**Loop syntax:** \`{{#each team sort="order" order="asc"}}\`
-
----
+When creating a new collection, you can start from a **template** that pre-configures common field sets:
 
-### Downloads (\`downloads\`)
-Downloadable files and documents.
+- **Blog Posts** - Articles with images, summary, body, author reference
+- **Authors** - Content creators with bio, photo, social links
+- **Team Members** - Staff profiles with role, photo, bio
+- **Downloads** - Downloadable files with description and category
+- **FAQs** - Question and answer pairs
+- **Products** - Items with price, description, images
 
-**Fields:**
-- \`{{title}}\` (text, required) - File title
-- \`{{slug}}\` (text) - URL slug
-- \`{{description}}\` (text) - Description
-- \`{{fileUrl}}\` (url) - Download link
-- \`{{category}}\` (select) - File category
-- \`{{order}}\` (number) - Display order
-
-**Loop syntax:** \`{{#each downloads sort="order" order="asc"}}\`
+Templates are just starting points - you can customize fields after creation.
 
 ---
 
-## Custom Collections
-
-Custom collections are tenant-defined content types created in the CMS dashboard. Each custom collection has its own slug and user-defined fields.
+## Token Syntax
 
-**Token syntax:** Same as built-in collections
-- \`{{fieldSlug}}\` for text, number, boolean, image, url, date, select fields
-- \`{{{fieldSlug}}}\` for richText fields (MUST use triple braces)
+### Basic Tokens
+\`\`\`html
+{{fieldSlug}}      <!-- For text, number, boolean, image, url, date, select -->
+{{{fieldSlug}}}    <!-- For richText fields (MUST use triple braces) -->
+\`\`\`
 
-**Required built-in tokens for ALL custom collections:**
+### Built-in Tokens (Available on ALL items)
 - \`{{name}}\` - Item name/title (REQUIRED - every item has a name)
-- \`{{slug}}\` - Item URL slug (if collection has detail pages enabled)
+- \`{{slug}}\` - Item URL slug (if collection has detail pages)
 - \`{{url}}\` - Full item URL (e.g., /services/my-service)
 
-**Date tokens (automatically tracked - available on all items):**
+### Date Tokens (Automatically tracked)
 - \`{{createdAt}}\` - When the item was first created
 - \`{{publishedAt}}\` - When the item was published (empty for drafts)
 - \`{{updatedAt}}\` - When the item was last updated
 
-**Example - A "Services" collection with fields: image, description (richText), price:**
-\`\`\`html
-<section class="services">
-  {{#each services sort="publishedAt" order="desc"}}
-  <div class="service-card">
-    <img src="{{image}}" alt="{{name}}">
-    <h2><a href="{{url}}">{{name}}</a></h2>
-    {{{description}}}
-    <p class="price">\${{price}}</p>
-    <time>{{publishedAt}}</time>
-  </div>
-  {{/each}}
-</section>
-\`\`\`
-
-**Example - A "Testimonials" collection with fields: quote (richText), company, rating:**
-\`\`\`html
-<section class="testimonials">
-  {{#each testimonials limit=6 sort="publishedAt" order="desc"}}
-  <blockquote class="testimonial">
-    {{{quote}}}
-    <cite>
-      <strong>{{name}}</strong>
-      {{#if company}}<span>{{company}}</span>{{/if}}
-    </cite>
-  </blockquote>
-  {{/each}}
-</section>
-\`\`\`
-
-**To see exact fields for a tenant's custom collections, use the \`get_tenant_schema\` tool.**
-
 ---
 
-## Custom Fields on Built-in Collections
-
-Tenants can add custom fields to Blog Posts, Authors, Team Members, and Downloads. These custom fields work exactly like built-in fields.
+## Loop Syntax
 
-**Token syntax:**
-- \`{{customFieldSlug}}\` for text, number, boolean, image, url, date, select
-- \`{{{customFieldSlug}}}\` for richText fields
-
-**Example - "category" field added to blogs:**
+### Basic Loop
 \`\`\`html
-{{#each blogs}}
-<article class="post-card">
-  <h2>{{name}}</h2>
-  {{#if category}}
-    <span class="category-badge">{{category}}</span>
-  {{/if}}
-  <p>{{postSummary}}</p>
-</article>
-{{/each}}
-\`\`\`
-
-**Example - "department" and "linkedinUrl" fields added to team:**
-\`\`\`html
-{{#each team sort="order" order="asc"}}
-<div class="team-member">
-  <img src="{{photo}}" alt="{{name}}">
-  <h3>{{name}}</h3>
-  <p class="role">{{role}}</p>
-  {{#if department}}
-    <p class="department">{{department}}</p>
-  {{/if}}
-  {{#if linkedinUrl}}
-    <a href="{{linkedinUrl}}">LinkedIn</a>
-  {{/if}}
-</div>
+{{#each collectionSlug}}
+  <article>
+    <h2>{{name}}</h2>
+  </article>
 {{/each}}
 \`\`\`
 
-**To see exact custom fields for a tenant, use the \`get_tenant_schema\` tool.**
-
----
-
-## Relation Fields
-
-Relation fields allow you to link items from one collection to items in another collection. This is similar to how blog posts can have an author reference.
-
-### Creating Relation Fields
-
-When creating a custom collection field, choose type "Relation" and select the target collection. You can link to:
-- Built-in collections: \`blogs\`, \`authors\`, \`team\`, \`downloads\`
-- Custom collections: Any collection you've created (e.g., \`tags\`, \`categories\`, \`services\`)
-
-### Using Relation Fields in Templates
-
-When an item has a relation field set, the related item's data is available using dot notation:
+### Loop Modifiers
+- \`limit=N\` - Limit to N items
+- \`featured=true\` - Only featured items (if collection has a boolean "featured" field)
+- \`sort="fieldName"\` - Sort by field
+- \`order="asc|desc"\` - Sort direction
 
 \`\`\`html
-<!-- Example: A "Projects" collection with a "category" relation field linking to "Categories" collection -->
-{{#each projects}}
-<article class="project-card">
-  <h2>{{name}}</h2>
-  {{#if category}}
-    <span class="category-tag">{{category.name}}</span>
-    <a href="{{category.url}}">View all {{category.name}} projects</a>
-  {{/if}}
-</article>
+{{#each posts limit=6 sort="publishedAt" order="desc"}}
+  <article>{{name}}</article>
 {{/each}}
 \`\`\`
 
-**Available tokens for related items:**
-- \`{{relationField.name}}\` - Related item's name
-- \`{{relationField.slug}}\` - Related item's slug
-- \`{{relationField.url}}\` - Related item's full URL
-- \`{{relationField.anyField}}\` - Any field from the related collection
-
-### Common Use Cases
-
-**Tags on Blog Posts:**
-\`\`\`html
-{{#each blogs}}
-<article>
-  <h2>{{name}}</h2>
-  {{#if tag}}
-    <span class="tag">{{tag.name}}</span>
-  {{/if}}
-</article>
-{{/each}}
-\`\`\`
+### Loop Variables
+Inside \`{{#each}}\` blocks:
+- \`{{@first}}\` - true for first item
+- \`{{@last}}\` - true for last item
+- \`{{@index}}\` - zero-based index
 
-**Category Pages - Filtering by Relation:**
 \`\`\`html
-<!-- On a category detail page, show items with this category -->
-{{#each projects}}
-  {{#if (eq category.slug ../slug)}}
-    <div class="project-card">
-      <h3>{{name}}</h3>
-    </div>
-  {{/if}}
+{{#each services limit=3}}
+  <div class="{{#if @first}}featured{{/if}}">
+    {{name}}
+  </div>
 {{/each}}
 \`\`\`
 
-**Related Services on Projects:**
-\`\`\`html
-{{#if relatedService}}
-<div class="related-service">
-  <h4>Service Used</h4>
-  <a href="{{relatedService.url}}">{{relatedService.name}}</a>
-  {{#if relatedService.description}}
-    <p>{{relatedService.description}}</p>
-  {{/if}}
-</div>
-{{/if}}
-\`\`\`
-
 ---
 
-## Template Syntax Reference
+## Conditionals
 
-### Loops
+### Check if field has value
 \`\`\`html
-{{#each blogs}}
-  <article>
-    <h2>{{name}}</h2>
-  </article>
-{{/each}}
-\`\`\`
-
-**Loop modifiers:**
-- \`limit=N\` - Limit to N items
-- \`featured=true\` - Only featured items
-- \`sort="fieldName"\` - Sort by field
-- \`order="asc|desc"\` - Sort direction
-
-### Conditionals
-\`\`\`html
-<!-- Check if a field has a value -->
-{{#if mainImage}}
-  <img src="{{mainImage}}" alt="{{name}}">
+{{#if image}}
+  <img src="{{image}}" alt="{{name}}">
 {{else}}
   <div class="placeholder"></div>
 {{/if}}
 
 {{#unless featured}}
-  <span>Regular post</span>
+  <span>Regular item</span>
 {{/unless}}
 \`\`\`
 
-### Collection Empty Checks (Page Level)
-Check if a collection has items - useful for "No posts yet" fallbacks:
-
+### Collection Empty Checks
 \`\`\`html
-{{#each blogs}}
+{{#each posts}}
   <article>{{name}}</article>
 {{/each}}
 
-{{#unless blogs}}
+{{#unless posts}}
   <p>No posts yet. Check back soon!</p>
 {{/unless}}
 \`\`\`
 
-**Important:** The \`{{#if blogs}}\` and \`{{#unless blogs}}\` syntax checks if the collection has any published items. Use this OUTSIDE of \`{{#each}}\` loops for empty state handling.
+---
+
+## Equality Comparisons
 
-### Equality Comparisons in Conditionals
-Compare two field values using the \`(eq field1 field2)\` helper:
+Compare field values using the \`(eq field1 field2)\` helper:
 
 \`\`\`html
 <!-- Show content when fields ARE equal -->
-{{#if (eq author.slug ../slug)}}
-  <span>This is your post!</span>
+{{#if (eq category.slug ../slug)}}
+  <span>Current category</span>
 {{/if}}
 
-<!-- Show content when fields are NOT equal -->
+<!-- Show content when fields are NOT equal (exclude current) -->
 {{#unless (eq slug ../slug)}}
   <a href="{{url}}">{{name}}</a>
 {{/unless}}
 \`\`\`
 
-**Common use case - Related Posts (exclude current):**
+### Related Items Pattern (Exclude Current)
 \`\`\`html
 <h3>Other Posts</h3>
-{{#each blogs limit=3}}
+{{#each posts limit=3}}
   {{#unless (eq slug ../slug)}}
     <article>
       <a href="{{url}}">{{name}}</a>
@@ -329,28 +145,15 @@ Compare two field values using the \`(eq field1 field2)\` helper:
 {{/each}}
 \`\`\`
 
-This pattern is essential for "Related Posts" sections where you want to show other posts but NOT the current one.
-
-### Loop Variables
-Inside \`{{#each}}\` blocks:
-- \`{{@first}}\` - true for first item
-- \`{{@last}}\` - true for last item
-- \`{{@index}}\` - zero-based index
+---
 
-\`\`\`html
-{{#each blogs limit=3}}
-  <article class="{{#if @first}}featured{{/if}}">
-    {{name}}
-  </article>
-{{/each}}
-\`\`\`
+## Parent Context References
 
-### Parent Context References (\`../\`)
-Inside loops, access the parent scope (page's current item) using \`../\`:
+Inside loops, access the parent scope using \`../\`:
 
 \`\`\`html
 <!-- On author detail page, show only posts by THIS author -->
-{{#each blogs}}
+{{#each posts}}
   {{#if (eq author.name ../name)}}
     <h3>{{name}}</h3>
   {{/if}}
@@ -361,186 +164,93 @@ Inside loops, access the parent scope (page's current item) using \`../\`:
 - \`../slug\` - Parent item's slug
 - \`../fieldName\` - Any field from the parent scope
 
-**Use cases:**
-- Author pages: filter posts by current author
-- Category pages: filter items by current category
-- Related items: match based on current detail page
+---
 
-### Equality Helpers Summary
+## Relation Fields
 
-| Syntax | When to use | Shows content when... |
-|--------|-------------|----------------------|
-| \`{{#if (eq field1 field2)}}\` | Compare two fields | Fields ARE equal |
-| \`{{#unless (eq field1 field2)}}\` | Exclude matches | Fields are NOT equal |
-| \`{{#eq field "value"}}\` | Compare to string | Field equals string |
+Link items from one collection to another. Access related item data using dot notation:
 
-**Examples:**
 \`\`\`html
-<!-- Show only when author matches current page -->
-{{#if (eq author.slug ../slug)}}...{{/if}}
+{{#each projects}}
+<article>
+  <h2>{{name}}</h2>
+  {{#if category}}
+    <span class="tag">{{category.name}}</span>
+    <a href="{{category.url}}">View all {{category.name}}</a>
+  {{/if}}
+</article>
+{{/each}}
+\`\`\`
 
-<!-- Show all EXCEPT current item (Related Posts pattern) -->
-{{#unless (eq slug ../slug)}}...{{/unless}}
+**Available tokens for related items:**
+- \`{{relationField.name}}\` - Related item's name
+- \`{{relationField.slug}}\` - Related item's slug
+- \`{{relationField.url}}\` - Related item's full URL
+- \`{{relationField.anyField}}\` - Any field from the related collection
 
-<!-- Compare field to a literal value -->
-{{#eq status "published"}}...{{/eq}}
-\`\`\`
+---
+
+## Rich Text (Triple Braces)
 
-### Rich Text (Triple Braces)
 For HTML content that should NOT be escaped:
 \`\`\`html
-{{{postBody}}}      ✓ Correct - renders HTML
-{{postBody}}        ✗ Wrong - escapes HTML as text
+{{{description}}}   ✓ Correct - renders HTML
+{{description}}     ✗ Wrong - escapes HTML as text
 \`\`\`
 
 ---
 
 ## Important Rules
 
-1. **Triple braces for richText fields** - \`{{{postBody}}}\`, \`{{{bio}}}\`
-2. **Double braces for everything else** - \`{{name}}\`, \`{{mainImage}}\`
+1. **Triple braces for richText fields** - \`{{{body}}}\`, \`{{{bio}}}\`
+2. **Double braces for everything else** - \`{{name}}\`, \`{{image}}\`
 3. **Always wrap optional fields in {{#if}}** - Check before rendering
 4. **Use {{url}} for links** - Generates correct path based on manifest
-5. **Match field names exactly** - \`{{name}}\` not \`{{title}}\`
+5. **Match field slugs exactly** - Case-sensitive
 
 ---
 
-## Image Handling in Templates
-
-### Two Types of Images
-
-**1. Static/UI Images** - Logos, icons, decorative backgrounds, UI elements
-- These are bundled with the site package
-- Use \`/public/\` paths
-- Keep these as static files
-
-**2. Content Images** - Blog photos, team headshots, product images, user-uploaded media
-- These are managed through the CMS dashboard
-- Use CMS tokens like \`{{mainImage}}\`, \`{{photo}}\`
-- Never hardcode example/placeholder content images
-
-### Static UI Images (Keep as /public/ paths)
-
-\`\`\`html
-<!-- These are CORRECT - static UI elements -->
-<img src="/public/images/logo.png" alt="Company Logo">
-<img src="/public/images/icons/arrow.svg" alt="">
-<div style="background-image: url('/public/images/hero-bg.jpg')">
-<link rel="icon" href="/public/images/favicon.ico">
-\`\`\`
-
-### Content Images (Use CMS Tokens)
+## Image Handling
 
+### Static UI Images (logos, icons)
 \`\`\`html
-<!-- These are CORRECT - CMS-managed content -->
-<img src="{{mainImage}}" alt="{{name}}">
-<img src="{{thumbnailImage}}" alt="{{name}}">
-<img src="{{photo}}" alt="{{name}}">
-
-<!-- WRONG - Don't hardcode example/placeholder content -->
-<img src="/images/sample-blog-post.jpg" alt="Sample Post">
-<img src="/images/placeholder-team.jpg" alt="Team Member">
+<img src="/public/images/logo.png" alt="Logo">
 \`\`\`
 
-### Image Field Pattern
-
-Always wrap image fields in conditionals since they may not be set:
-
+### CMS Content Images
 \`\`\`html
-{{#if mainImage}}
-  <img src="{{mainImage}}" alt="{{name}}" class="hero-image">
+{{#if heroImage}}
+  <img src="{{heroImage}}" alt="{{name}}">
 {{/if}}
 \`\`\`
 
-### Custom Collection Image Fields
-
-For custom collections, the **token name matches the field slug** defined when creating the collection.
-
-**Example:** A "video" collection with these fields:
-- \`videothumbnail\` (type: image)
-- \`ogimage\` (type: image)
-- \`shortdescription\` (type: text)
-
-**Template uses the field slugs as tokens:**
-\`\`\`html
-{{#each video sort="publishedAt" order="desc"}}
-<article class="video-card">
-  {{#if videothumbnail}}
-    <img src="{{videothumbnail}}" alt="{{name}}">
-  {{/if}}
-  <h2><a href="{{url}}">{{name}}</a></h2>
-  <p>{{shortdescription}}</p>
-</article>
-{{/each}}
-\`\`\`
-
-**To find exact field slugs for a tenant's custom collections, use the \`get_tenant_schema\` tool.**
-
-### Common Mistakes to Avoid
-
-1. **Replacing logos/icons with CMS tokens** - Static UI images should stay as \`/public/\` paths
-2. **Hardcoding example blog/product content** - Use \`{{#each}}\` loops with CMS tokens
-3. **Missing \`{{#each}}\` loops** - Dynamic content requires iteration over the collection
-4. **Wrong field names** - Token must match the exact field slug (case-sensitive)
-
 ---
 
 ## CMS Template Configuration
 
-Templates are configured in manifest.json using a **flat format** that is the SINGLE SOURCE OF TRUTH for URL paths.
+Configure templates in manifest.json:
 
-### manifest.json Format
 \`\`\`json
 {
   "cmsTemplates": {
-    // Built-in: Blog
-    "blogIndex": "pages/blog.html",
-    "blogIndexPath": "/blog",
-    "blogPost": "templates/blog-post.html",
-    "blogPostPath": "/blog",
-    
-    // Built-in: Team, Downloads, Authors
-    "team": "pages/team.html",
-    "teamPath": "/team",
-    "downloads": "pages/downloads.html",
-    "downloadsPath": "/resources",
-    "authorsIndex": "pages/authors.html",
-    "authorsIndexPath": "/authors",
+    "postsIndex": "pages/blog.html",
+    "postsIndexPath": "/blog",
+    "postsDetail": "templates/blog-post.html",
+    "postsDetailPath": "/blog",
     
-    // Custom Collections: Use {slug}Index, {slug}Detail, {slug}IndexPath, {slug}DetailPath
-    "videoIndex": "pages/videos.html",
-    "videoIndexPath": "/videos",
-    "videoDetail": "templates/video-detail.html",
-    "videoDetailPath": "/videos",
-    
-    "serviceIndex": "pages/services.html",
-    "serviceIndexPath": "/services",
-    "serviceDetail": "templates/service-detail.html",
-    "serviceDetailPath": "/service"
+    "servicesIndex": "pages/services.html",
+    "servicesIndexPath": "/services",
+    "servicesDetail": "templates/service-detail.html",
+    "servicesDetailPath": "/services"
   }
 }
 \`\`\`
 
-### Custom Collection URL Routing
-
-**IMPORTANT:** The collection's internal slug (set in CMS) is for database only, NOT for URLs.
-URL paths come EXCLUSIVELY from the manifest's \`{slug}IndexPath\` and \`{slug}DetailPath\`.
-
-**Example:** Collection with slug \`video\` but paths \`/videos\` and \`/videos/:itemSlug\`:
-- \`videoIndexPath: "/videos"\` → Index page at \`/videos\`
-- \`videoDetailPath: "/videos"\` → Detail pages at \`/videos/my-video\`
-
-**Different paths for index and detail:**
-- \`serviceIndexPath: "/services"\` → Index at \`/services\`
-- \`serviceDetailPath: "/service"\` → Detail at \`/service/my-service\`
-
-### Template Types
-- **{slug}Index** - Template file for the index/listing page
-- **{slug}IndexPath** - URL path for the index page
-- **{slug}Detail** - Template file for the detail page
-- **{slug}DetailPath** - URL path base for detail pages (item slug appended)
-
-**Note:** The CMS settings UI can also configure these, but manifest.json takes precedence for AI conversions.
+### Template Keys Pattern
+- **{collectionSlug}Index** - Template file for listing page
+- **{collectionSlug}IndexPath** - URL path for listing page
+- **{collectionSlug}Detail** - Template file for detail page
+- **{collectionSlug}DetailPath** - URL base for detail pages
 
 ---
 
@@ -548,10 +258,6 @@ URL paths come EXCLUSIVELY from the manifest's \`{slug}IndexPath\` and \`{slug}D
 
 Forms are automatically captured and stored in the CMS.
 
-### Form Setup
-1. Add \`data-form-name="xxx"\` attribute to the form
-2. Include the form handler script in your JavaScript
-
 \`\`\`html
 <form data-form-name="contact">
   <input type="text" name="firstName" required>
@@ -561,7 +267,7 @@ Forms are automatically captured and stored in the CMS.
 </form>
 \`\`\`
 
-### Form Handler Script (add to /public/js/main.js)
+### Form Handler Script
 \`\`\`javascript
 document.querySelectorAll('form[data-form-name]').forEach(form => {
   form.addEventListener('submit', async (e) => {
@@ -586,55 +292,29 @@ document.querySelectorAll('form[data-form-name]').forEach(form => {
 
 **CRITICAL:** Endpoint is \`/_forms/{formName}\` - NOT \`/api/forms/submit\`
 
-### Common Form Names
-- \`contact\` - Contact/inquiry forms
-- \`newsletter\` - Email signups
-- \`quote-request\` - Quote/consultation requests
-- \`appointment\` - Scheduling forms
+---
+
+## SEO Template Tokens
+
+For CMS detail pages, use tokens in SEO templates:
+- \`{{name}}\` - Item name for title
+- \`{{description}}\` or summary field - For meta description
+- \`{{image}}\` field - For OG image
 
-Tenant context is handled automatically by the system.
+SEO templates are configured in the Fast Mode Editor.
 
 ---
 
-## SEO Template Tokens
+## Next Steps
 
-For CMS detail pages (like blog posts), Fast Mode supports **token-based SEO templates**. These allow dynamic SEO meta tags where tokens are replaced with the actual item data at render time.
-
-**⚠️ IMPORTANT:** Do NOT include hardcoded SEO tags in templates. Fast Mode strips them and replaces with configured settings.
-
-### Available SEO Tokens by Collection
-
-#### Blog Posts (\`blogs\`)
-| Token | Use For | Example Output |
-|-------|---------|----------------|
-| \`{{name}}\` | Meta Title | "How to Build a Website" |
-| \`{{postSummary}}\` | Meta Description | "Learn the fundamentals..." |
-| \`{{mainImage}}\` | OG Image | "https://cdn.example.com/hero.jpg" |
-| \`{{author.name}}\` | Author Attribution | "Jane Smith" |
-
-**Example SEO Template for Blog:**
-- Meta Title: \`{{name}} | {{author.name}} | My Blog\`
-- Meta Description: \`{{postSummary}}\`
-- OG Image: \`{{mainImage}}\`
-
-#### Authors (\`authors\`)
-| Token | Use For |
-|-------|---------|
-| \`{{name}}\` | Meta Title |
-| \`{{bio}}\` | Meta Description |
-| \`{{picture}}\` | OG Image |
-
-#### Custom Collections
-All custom field tokens are available:
-- \`{{name}}\` - Item name
-- \`{{slug}}\` - URL slug
-- \`{{customFieldSlug}}\` - Any custom field
-
-Date tokens (automatically tracked):
-- \`{{createdAt}}\` - When the item was created
-- \`{{publishedAt}}\` - When the item was published
-- \`{{updatedAt}}\` - When the item was last updated
+**To see exact collections and fields for a specific project, use:**
+\`\`\`
+get_tenant_schema(projectId: "your-project-name-or-id")
+\`\`\`
 
-SEO templates are configured in the Fast Mode Editor when viewing CMS detail pages (e.g., \`/blog/:slug\`).
+This will show you:
+- All collections with their slugs
+- All fields with their tokens, types, and descriptions
+- Relation field targets
 `;
 }