Skip to main content
Glama

Update a post's settings

update_post_settings
Idempotent

On one site of the account, named in site. The drawer's fields, any subset: title, slug (blank regenerates from the title), subtitle (the line under the title, inline Markdown: italic, bold, a link; blank removes it), tags (the whole list, names), authors (the whole list in byline order, staff slugs or names; editors and above), featured, comments (whether members may comment; a post starts open, a page closed), visibility, tiers and circles (who reads past the excerpt), meta title and description, the cover's alt and caption, header layout, a page's place in a collection (collection for its top level, parent_id to go under a page, collection "" to leave), and a collection page's fields. Content is edit_post's; status is publish_post's. Many posts at once is change_posts'.

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": {
      "site": "<site>",
      "post_id": "<post_id>"
    },
    "name": "update_post_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site to work on, as list_sites names it
slugNo
tagsNo
tiersNoTier names, for visibility specific: the whole list
titleNo
fieldsNoA page's field values by name, for the fields its collection's level names (get_collection gives them): {"location": {"lat": -33.89, "lng": 151.27}, "break": "Reef"}. A field left out keeps its value; null clears it
authorsNoThe whole list, first leading the byline: staff slugs or names
circlesNoCircle names or slugs, for visibility specific, where the publication has circles: the whole list
post_idYes
commentsNo
featuredNo
subtitleNo
parent_idNoThe page it goes under, in that page's collection (get_collection gives the ids)
collectionNoA collection's id, slug or name: the page goes on its top level. "" takes it out of every collection
meta_titleNo
visibilityNoWho reads past the excerpt: public (everyone), members (any signed-in member), paid (a paying or comped member), specific (a member on any tier named in tiers or in any circle named in circles; name at least one)
header_layoutNo
meta_descriptionNo
feature_image_altNo
feature_image_captionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=true), and the description adds genuinely non-obvious behavior on top: blank slug regenerates from title, blank subtitle removes it, tags/authors/tiers/circles are whole-list replacements, collection "" removes from every collection, and authors editing requires 'editors and above'. It still says nothing about failure modes, auth scope generally, or what the call returns, so it stops short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Given 20 parameters, the length is defensible and nearly every clause carries information. But the prose is a single run-on of nested parentheses, it opens with a fragment ('On one site of the account, named in site.'), and the highest-value routing information is buried at the end where it is likely to be skimmed past.

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 20-parameter mutation tool with a nested 'fields' object and no output schema, the definition covers essentially every settable field and its edge semantics. Remaining gaps are small: header_layout options, whether omitted fields are preserved (implied by 'any subset' but not stated for scalars), and no notion of the response.

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?

With schema coverage at only 40% across 20 params, the description carries real weight and delivers: whole-list semantics for tags/authors/tiers/circles, byline ordering, 'editors and above' permission on authors, blank-value behavior for slug and subtitle, and the collection/parent_id/"" placement triad. It leaves header_layout's three options and post_id unexplained, and defers all 'fields' nested-object detail to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates exactly which settings are touched (title, slug, subtitle, tags, authors, featured, comments, visibility, tiers/circles, meta, cover alt/caption, header layout, collection placement) and explicitly fences off siblings: "Content is edit_post's; status is publish_post's. Many posts at once is change_posts'." The only weakness is that the body never states the action verb in a sentence of its own — 'The drawer's fields, any subset' implies assignment and leans on the title for 'update'.

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?

It names three alternative tools and the exact condition that selects each: content goes to edit_post, status to publish_post, bulk to change_posts. It also states 'any subset', which tells the agent partial updates are legal and nothing else is required.

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