Skip to main content
Glama

Update post

update_post
Idempotent

Edit an existing post. Pass the post's slug and a patch of fields to change; coverImage: null removes the cover. Use this when the user wants a published post or draft changed. patch: { status: "draft" } takes a live post offline and "published" puts a draft live. Slug itself can't change; delete and republish if you need a new URL. Afterwards, give the user the returned post_url when the post is published. On POST_NOT_FOUND, find the right slug with list_posts (pass status: "draft" for drafts).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesSlug of the post, e.g. "hello-world", as returned by create_post or list_posts.
patchYesFields to change; omitted fields stay as they are. Same fields as create_post except `slug`, which cannot change.
blog_idNoYour blog's id, as returned by signup. Optional with an API key: it defaults to the key's blog, and any id you pass must be that blog. Required when the server runs without API keys.
idempotency_keyNoOptional retry key, any unique string (e.g. a UUID). Retrying with the same key and identical arguments returns the first result instead of writing again; the same key with different arguments fails with IDEMPOTENCY_KEY_CONFLICT. Scoped to your API key and this tool.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
postNo
errorNoPresent only on failure (isError: true). Success fields are absent then.
post_urlNoLive URL of the post. Present only when it is published.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.