Skip to main content
Glama

Update landing page draft

postfjord_update_page
DestructiveIdempotent

Changes a page's draft: title, blocks, description, search title, style, motion, Hide from Google (hideFromSearch), or when a landing page is online (liveFrom, liveUntil). Send only what changes; blocks replaces the whole list, so send every block that stays, with its id from postfjord_get_page. A published page stays live with the version that was published, as in the app, until it is published again with postfjord_publish_page. The answer has the page and the checks that still stop a publish.

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": {
      "pageId": "<pageId>"
    },
    "name": "postfjord_update_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNoA new style resets the colours to the style's, with the brand kit's on top unless useBrand is false.
titleNoThe page's name, up to 60 characters.
blocksNoThe blocks from top to bottom. A link in bio page is usually: a hero with layout avatar (the business name, a short line and a photo), a links block with the most important links, and a social block. A landing page for one offer: a hero, a text, a list or faq, a button or a form block. A countdown block (date, time, tz, units, button { label, href }, after, afterText, afterButton) counts down to a date, like a launch or the last day to sign up: use only a real date the person gave, and never move a deadline that has passed to a later one. A location block (name is the business name here; street, city, region, postal, country, phone, tz, week, exceptions) shows the address, opening hours with Open now, a Call button and map links: use only hours and an address the user gave you; never invent them. For a class, call or appointment, use a booking block with the booking link; never invent a link. Write real facts only; do not invent prices, dates or quotes. Text in [brackets] stops a publish; a link written [words](https://address) in a text, the hero line or a faq answer is a link, not brackets, and [words]{#rrggbb} gives those words a color (only when the user asks for one). Any block, and any row of a links block, can show only from one time until another (show).
motionNotrue: sections fade in as visitors scroll and photos settle into place; false: the page stands still. New pages start with true. People who ask their device for less motion always see a still page. On a live page the change goes live with the next postfjord_publish_page.
pageIdYes
liveFromNoLanding pages only: when visitors can see the whole page, as a date and time with an offset or a local time in the workspace time zone (timeZone in postfjord_get_page). Before liveFrom the address says the page does not exist; after liveUntil visitors see that it has ended. null removes it. The link in bio page cannot be scheduled as a whole.
seoTitleNoA title for Google and shared links, up to 70 characters.
useBrandNo
liveUntilNoLanding pages only: when visitors can see the whole page, as a date and time with an offset or a local time in the workspace time zone (timeZone in postfjord_get_page). Before liveFrom the address says the page does not exist; after liveUntil visitors see that it has ended. null removes it. The link in bio page cannot be scheduled as a whole.
descriptionNoWhat Google and shared links show under the title, up to 200 characters.
hideFromSearchNoLanding pages only: true keeps the page out of Google and other search engines (a robots noindex tag, and it leaves the sitemap), so only people with the link find it. On a live page the change goes live with the next postfjord_publish_page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • changedInput schema / properties / blocks / items / properties / columns / description
      Previous value: -"features: 2 or 3. products: 2 or 3."New value: +"features: 2 or 3. products: 1 (one to a row, photo beside the words), 2 or 3."
    • addedInput schema / properties / blocks / items / properties / focus
      Added value: +{
      +  "description": "hero: the part of the photo that stays in view when it is cropped, as \"x y\" from 0 to 100, like \"50 10\" for near the top in the middle.",
      +  "type": "string"
      +}
    • changedInput schema / properties / blocks / items / properties / href / description
      Previous value: -"button, booking, image, video: the link. booking: the booking page itself, never #form or mailto:."New value: +"button, booking, image, video, music: the link. music: only a Spotify, Apple Music or SoundCloud address; the player loads when a visitor taps. booking: the booking page itself, never #form or mailto:."
    • changedInput schema / properties / blocks / items / properties / items / description
      Previous value: -"links, social, list, faq: the rows. products: the products, kept as they are."New value: +"links, social, list, faq: the rows. products: the products, kept as they are; a card by hand is { title, href, mediaId, priceText (like $19), text }. list and gallery rows take an optional href, so a visitor can tap them. A links row with a mediaId takes big: true for a large card with the photo on top. social networks include spotify, applemusic and soundcloud."
    • addedInput schema / properties / blocks / items / properties / items / items / properties / big
      Added value: +{
      +  "description": "links, on a row with a mediaId: a large card with the photo on top.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / blocks / items / properties / items / items / properties / network / description
      Previous value: -"social: instagram, tiktok, youtube, facebook, x, threads, linkedin, pinterest, website or email."New value: +"social: instagram, tiktok, youtube, spotify, applemusic, soundcloud, facebook, x, threads, linkedin, pinterest, bluesky, mastodon, reddit, snapchat, website or email."
    • addedInput schema / properties / blocks / items / properties / items / items / properties / priceText
      Added value: +{
      +  "description": "products, a card by hand: the price as you would say it, like $19. Use only a price the user gave you.",
      +  "type": "string"
      +}
    • changedInput schema / properties / blocks / items / properties / layout / description
      Previous value: -"hero: avatar (round photo, for link in bio), center, cover (photo behind), split or photo (a full screen photo, darkened, with the words on it; place says where). gallery: grid, masonry or strip. list: cards, rows, menu, checks or steps. booking: card (a box with a heading, a few lines and the button) or button (the button alone)."New value: +"hero: avatar (round photo, for link in bio), center, cover (photo behind), banner (a short photo edge to edge, so links show on the first screen), split or photo (a full screen photo, darkened, with the words on it; place says where). gallery: grid, masonry or strip. list: cards, rows, menu, checks or steps. booking: card (a box with a heading, a few lines and the button) or button (the button alone)."
    • addedInput schema / properties / blocks / items / properties / scale
      Added value: +{
      +  "description": "hero and heading: bigger words than the look gives, up to poster type. Left out, the look decides.",
      +  "enum": [
      +    "l",
      +    "xl",
      +    "xxl"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / blocks / items / properties / type / description
      Previous value: -"hero: the header with the name and a photo. text, heading, image, links (link buttons), button, booking (a button that opens a booking page: Calendly, Cal.com, Acuity, Mindbody, Square, Google Calendar or any https link), social (social icons), share (buttons that let visitors share the page on WhatsApp, email, X and LinkedIn), form (a signup form), countdown (a date to count down to, like a launch or the last day to sign up; use only a real date the person gave), location (the business address, opening hours, a Call button and map links; use only hours and an address the user gave you, never invent them), products (Shopify products the person picked in the app, each { title, href, mediaId, price }; keep them as postfjord_get_page gives them and never invent one), split (photo and text rows, items [{ mediaId, alt, eyebrow, heading, text, label, href }], start left or right), gallery (photos, layout grid, masonry or strip, items [{ mediaId, alt, caption }]), slider (slides people swipe, items [{ mediaId, alt, text (a quote), name }]), stats (up to 4 big numbers, items [{ value, label }]; only real numbers the person gave), features (points with an icon, columns 2 or 3, items [{ icon, title, text }], icon a name like star, heart, clock, mapPin, leaf, sparkles, users, sun), pricing (2 to 4 plans, items [{ name, price, period, text, features (one per line), label, href, featured }], one featured at most; only real prices), reviews (customer words as cards, items [{ text, name, detail, mediaId }]; only real reviews, never invent one), and the editor's other blocks: posts, video, list, quote, faq, spacer."New value: +"hero: the header with the name and a photo. music: a Spotify, Apple Music or SoundCloud player (href, title, mediaId). products: photo, price and buy link, by hand or from a store. text, heading, image, links (link buttons), button, booking (a button that opens a booking page: Calendly, Cal.com, Acuity, Mindbody, Square, Google Calendar or any https link), social (social icons), share (buttons that let visitors share the page on WhatsApp, email, X and LinkedIn), form (a signup form), countdown (a date to count down to, like a launch or the last day to sign up; use only a real date the person gave), location (the business address, opening hours, a Call button and map links; use only hours and an address the user gave you, never invent them), products (Shopify products the person picked in the app, each { title, href, mediaId, price }; keep them as postfjord_get_page gives them and never invent one), split (photo and text rows, items [{ mediaId, alt, eyebrow, heading, text, label, href }], start left or right), gallery (photos, layout grid, masonry or strip, items [{ mediaId, alt, caption }]), slider (slides people swipe, items [{ mediaId, alt, text (a quote), name }]), stats (up to 4 big numbers, items [{ value, label }]; only real numbers the person gave), features (points with an icon, columns 2 or 3, items [{ icon, title, text }], icon a name like star, heart, clock, mapPin, leaf, sparkles, users, sun), pricing (2 to 4 plans, items [{ name, price, period, text, features (one per line), label, href, featured }], one featured at most; only real prices), reviews (customer words as cards, items [{ text, name, detail, mediaId }]; only real reviews, never invent one), and the editor's other blocks: posts, video, list, quote, faq, spacer."
    • changedInput schema / properties / blocks / items / properties / type / enum
      Previous value: -[
      -  "hero",
      -  "heading",
      -  "text",
      -  "image",
      -  "products",
      -  "split",
      -  "slider",
      -  "gallery",
      -  "links",
      -  "button",
      -  "booking",
      -  "countdown",
      -  "form",
      -  "social",
      -  "location",
      -  "share",
      -  "posts",
      -  "video",
      -  "list",
      -  "features",
      -  "pricing",
      -  "stats",
      -  "quote",
      -  "reviews",
      -  "faq",
      -  "spacer"
      -]New value: +[
      +  "hero",
      +  "heading",
      +  "text",
      +  "image",
      +  "products",
      +  "split",
      +  "slider",
      +  "gallery",
      +  "links",
      +  "button",
      +  "booking",
      +  "countdown",
      +  "form",
      +  "social",
      +  "location",
      +  "share",
      +  "posts",
      +  "video",
      +  "music",
      +  "list",
      +  "features",
      +  "pricing",
      +  "stats",
      +  "quote",
      +  "reviews",
      +  "faq",
      +  "spacer"
      +]
  2. Changed9 schema fields changed
    • addedInput schema / properties / blocks / items / properties / bg
      Added value: +{
      +  "anyOf": [
      +    {
      +      "properties": {
      +        "dim": {
      +          "type": "number"
      +        },
      +        "fill": {
      +          "enum": [
      +            "soft",
      +            "accent",
      +            "ink",
      +            "photo"
      +          ],
      +          "type": "string"
      +        },
      +        "mediaId": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "required": [
      +        "fill"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Any block: a background for its section, edge to edge. soft (a light tint), accent (the accent colour), ink (the page colours turned around) or photo with mediaId (from postfjord_list_media) and dim 55, 65 or 75 (how much darker in %, 65 by default; each keeps white words easy to read). null removes it."
      +}
    • addedInput schema / properties / blocks / items / properties / columns
      Added value: +{
      +  "description": "features: 2 or 3. products: 2 or 3.",
      +  "type": "string"
      +}
    • changedInput schema / properties / blocks / items / properties / layout / description
      Previous value: -"hero: avatar (round photo, for link in bio), center, cover (photo behind) or split. list: cards, rows, menu, checks or steps. booking: card (a box with a heading, a few lines and the button) or button (the button alone)."New value: +"hero: avatar (round photo, for link in bio), center, cover (photo behind), split or photo (a full screen photo, darkened, with the words on it; place says where). gallery: grid, masonry or strip. list: cards, rows, menu, checks or steps. booking: card (a box with a heading, a few lines and the button) or button (the button alone)."
    • addedInput schema / properties / blocks / items / properties / place
      Added value: +{
      +  "description": "hero with layout photo: where the words sit on the photo, center by default.",
      +  "enum": [
      +    "left",
      +    "center",
      +    "bottom"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / blocks / items / properties / space
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "compact",
      +        "normal",
      +        "airy"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Any block: the space above and below its section. normal by default."
      +}
    • addedInput schema / properties / blocks / items / properties / start
      Added value: +{
      +  "description": "split: the side of the first photo; the rows change sides from there.",
      +  "enum": [
      +    "left",
      +    "right"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / blocks / items / properties / type / description
      Previous value: -"hero: the header with the name and a photo. text, heading, image, links (link buttons), button, booking (a button that opens a booking page: Calendly, Cal.com, Acuity, Mindbody, Square, Google Calendar or any https link), social (social icons), share (buttons that let visitors share the page on WhatsApp, email, X and LinkedIn), form (a signup form), countdown (a date to count down to, like a launch or the last day to sign up; use only a real date the person gave), location (the business address, opening hours, a Call button and map links; use only hours and an address the user gave you, never invent them), products (Shopify products the person picked in the app, each { title, href, mediaId, price }; keep them as postfjord_get_page gives them and never invent one), and the editor's other blocks: posts, video, list, quote, faq, spacer."New value: +"hero: the header with the name and a photo. text, heading, image, links (link buttons), button, booking (a button that opens a booking page: Calendly, Cal.com, Acuity, Mindbody, Square, Google Calendar or any https link), social (social icons), share (buttons that let visitors share the page on WhatsApp, email, X and LinkedIn), form (a signup form), countdown (a date to count down to, like a launch or the last day to sign up; use only a real date the person gave), location (the business address, opening hours, a Call button and map links; use only hours and an address the user gave you, never invent them), products (Shopify products the person picked in the app, each { title, href, mediaId, price }; keep them as postfjord_get_page gives them and never invent one), split (photo and text rows, items [{ mediaId, alt, eyebrow, heading, text, label, href }], start left or right), gallery (photos, layout grid, masonry or strip, items [{ mediaId, alt, caption }]), slider (slides people swipe, items [{ mediaId, alt, text (a quote), name }]), stats (up to 4 big numbers, items [{ value, label }]; only real numbers the person gave), features (points with an icon, columns 2 or 3, items [{ icon, title, text }], icon a name like star, heart, clock, mapPin, leaf, sparkles, users, sun), pricing (2 to 4 plans, items [{ name, price, period, text, features (one per line), label, href, featured }], one featured at most; only real prices), reviews (customer words as cards, items [{ text, name, detail, mediaId }]; only real reviews, never invent one), and the editor's other blocks: posts, video, list, quote, faq, spacer."
    • changedInput schema / properties / blocks / items / properties / type / enum
      Previous value: -[
      -  "hero",
      -  "heading",
      -  "text",
      -  "image",
      -  "products",
      -  "links",
      -  "button",
      -  "booking",
      -  "countdown",
      -  "form",
      -  "social",
      -  "location",
      -  "share",
      -  "posts",
      -  "video",
      -  "list",
      -  "quote",
      -  "faq",
      -  "spacer"
      -]New value: +[
      +  "hero",
      +  "heading",
      +  "text",
      +  "image",
      +  "products",
      +  "split",
      +  "slider",
      +  "gallery",
      +  "links",
      +  "button",
      +  "booking",
      +  "countdown",
      +  "form",
      +  "social",
      +  "location",
      +  "share",
      +  "posts",
      +  "video",
      +  "list",
      +  "features",
      +  "pricing",
      +  "stats",
      +  "quote",
      +  "reviews",
      +  "faq",
      +  "spacer"
      +]
    • addedInput schema / properties / motion
      Added value: +{
      +  "description": "true: sections fade in as visitors scroll and photos settle into place; false: the page stands still. New pages start with true. People who ask their device for less motion always see a still page. On a live page the change goes live with the next postfjord_publish_page.",
      +  "type": "boolean"
      +}
  3. Changed3 schema fields changed
    • addedInput schema / properties / description / description
      Added value: +"What Google and shared links show under the title, up to 200 characters."
    • addedInput schema / properties / seoTitle / description
      Added value: +"A title for Google and shared links, up to 70 characters."
    • addedInput schema / properties / title / description
      Added value: +"The page's name, up to 60 characters."
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Explains why destructiveHint applies: blocks replaces the whole list, so any block left out is lost. It also says a published page keeps its live version until republished, and that the response includes the page plus the checks that still block a publish. All of this goes beyond the annotations and does not contradict them.

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?

Four dense sentences that each matter, front-loaded with purpose. The wording is slightly awkward in places ("The answer has the page"), but there is no waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex mutation tool with no output schema, it briefly covers the return value, the draft-versus-live distinction and the replacement trap. Combined with the very rich schema, an agent has what it needs, though permissions and errors are not mentioned.

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 high, but the description adds key semantics: partial-update behavior, full replacement of blocks, preserving ids, and maps hideFromSearch and liveFrom/liveUntil to their plain-language meanings. pageId has no description anywhere, a small gap.

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 the verb and resource, "Changes a page's draft", and lists the editable fields. It separates the tool from postfjord_publish_page by noting that publishing is a separate step, and from postfjord_get_page as the source of block ids.

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 clear workflow: send only what changes, fetch block ids from postfjord_get_page first, then publish with postfjord_publish_page. It does not say when to use postfjord_create_page instead, though that is fairly obvious.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources