Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_blog_update_post

Idempotent

Updates an existing blog post's content, status, metadata, tags, and publishing settings for a specified blog site, so you can revise or reschedule posts without recreating them.

Instructions

Update Blog Post The "Update Blog Post" API updates an existing blog post for any given blog site. Endpoint: PUT /blogs/posts/{postId} (Version header: v3; source: v3/blogs-v3.json) Requires a Sub-Account (location) token. OAuth scopes: blogs/post-update.write

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": {
      "postId": "<postId>",
      "body": "<body>"
    },
    "name": "ghl_blog_update_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
postIdYesIdentifier of the blog post to fetch

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed51 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / archived
      Added value: +{
      +  "description": "Whether the blog post is archived",
      +  "example": false,
      +  "type": "boolean"
      +}
    • addedInput schema / properties / body / properties / assistModeData
      Added value: +{
      +  "description": "Assist-mode configuration captured at the time of generation",
      +  "example": {
      +    "tone": "professional",
      +    "topic": "How to improve customer engagement using AI",
      +    "wordLimit": "1000-1500"
      +  },
      +  "type": "object"
      +}
    • changedInput schema / properties / body / properties / author / description
      Previous value: -"This needs to be author id, which you can get from the author get api call."New value: +"Identifier of the author of the blog post"
    • changedInput schema / properties / body / properties / author / example
      Previous value: -"6683abde331c041f32c07aea"New value: +"659ec9634a3796e4e47cc360"
    • changedInput schema / properties / body / properties / blogId / description
      Previous value: -"You can find the blog id from blog site dashboard link"New value: +"Identifier of the blog site the post belongs to"
    • changedInput schema / properties / body / properties / blogId / example
      Previous value: -"Blog ID"New value: +"lMOzIQZne5m6zQ528sT6"
    • addedInput schema / properties / body / properties / canonicalLink / description
      Added value: +"Canonical link override for SEO"
    • changedInput schema / properties / body / properties / canonicalLink / example
      Previous value: -"https://tryghl.blog/post/testing-unsplash"New value: +"https://example.com/blog/my-blog-post"
    • changedInput schema / properties / body / properties / categories / description
      Previous value: -"This needs to be array of category ids, which you can get from the category get api call."New value: +"Identifiers of categories the blog post belongs to"
    • changedInput schema / properties / body / properties / categories / example
      Previous value: -[
      -  "9c48df2694a849b6089f9d0d3513efe",
      -  "6683abde331c041f32c07aee"
      -]New value: +[
      +  "659ecabc4a37969a2b7cc370"
      +]
    • addedInput schema / properties / body / properties / conversationHistoryPath
      Added value: +{
      +  "description": "Storage path of the conversation history for AI-assisted edits",
      +  "example": "conversations/blog/64a1b2c3d4e5f6a7b8c9d0e1.json",
      +  "type": "string"
      +}
    • addedInput schema / properties / body / properties / currentVersion
      Added value: +{
      +  "description": "Identifier of the current version of the blog post",
      +  "example": "66c381b38be80858b9af62b7",
      +  "type": "string"
      +}
    • addedInput schema / properties / body / properties / description / description
      Added value: +"Short description or excerpt for the blog post"
    • changedInput schema / properties / body / properties / description / example
      Previous value: -"A short description"New value: +"A practical guide to inbound marketing in 2026."
    • addedInput schema / properties / body / properties / externalFonts
      Added value: +{
      +  "description": "External fonts referenced by the blog post body",
      +  "example": [
      +    "Inter",
      +    "Merriweather"
      +  ],
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / body / properties / imageAltText / description
      Added value: +"Alt text for the cover image"
    • changedInput schema / properties / body / properties / imageAltText / example
      Previous value: -"Alt text for your blog image"New value: +"A laptop on a desk"
    • addedInput schema / properties / body / properties / imageUrl / description
      Added value: +"Cover image URL for the blog post"
    • changedInput schema / properties / body / properties / imageUrl / example
      Previous value: -"Image URl"New value: +"https://storage.googleapis.com/blog-assets/posts/cover.png"
    • addedInput schema / properties / body / properties / importId
      Added value: +{
      +  "description": "Identifier of the import record this post was created from",
      +  "example": "64a1b2c3d4e5f6a7b8c9d0e1",
      +  "type": "string"
      +}
    • addedInput schema / properties / body / properties / isAIGenerated
      Added value: +{
      +  "deprecated": true,
      +  "description": "Deprecated. Use `isAiGenerated` instead. Kept for backwards compatibility.",
      +  "example": false,
      +  "type": "boolean"
      +}
    • addedInput schema / properties / body / properties / isAiGenerated
      Added value: +{
      +  "description": "Whether the blog post was generated using AI assistance",
      +  "example": false,
      +  "type": "boolean"
      +}
    • addedInput schema / properties / body / properties / isAutoSave
      Added value: +{
      +  "description": "Whether this update is an automatic save from the editor",
      +  "example": false,
      +  "type": "boolean"
      +}
    • addedInput schema / properties / body / properties / locationId / description
      Added value: +"Sub-account (location) identifier the blog post belongs to"
    • changedInput schema / properties / body / properties / locationId / example
      Previous value: -"Location ID"New value: +"ve9EPM428h8vShlRW1KT"
    • addedInput schema / properties / body / properties / metaData
      Added value: +{
      +  "description": "Metadata about actors that performed lifecycle actions on the post",
      +  "example": {
      +    "publishedBy": "user_abc123",
      +    "updatedBy": "user_abc123"
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / body / properties / originId
      Added value: +{
      +  "description": "External identifier when the post was imported from another system",
      +  "example": "wp-post-42",
      +  "type": "string"
      +}
    • changedInput schema / properties / body / properties / publishedAt / description
      Previous value: -"Provide ISO timestamp"New value: +"Timestamp when the post was (or will be) published"
    • changedInput schema / properties / body / properties / publishedAt / example
      Previous value: -"2025-02-05T18:30:47.000Z"New value: +"2026-05-13T17:14:57.000Z"
    • addedInput schema / properties / body / properties / rawHTML / description
      Added value: +"Full HTML body of the blog post"
    • changedInput schema / properties / body / properties / rawHTML / example
      Previous value: -"<h1>Your blog content</h1>"New value: +"<h1>Hello</h1><p>This is my post.</p>"
    • addedInput schema / properties / body / properties / readTimeInMinutes
      Added value: +{
      +  "description": "Estimated read time of the blog post, in minutes",
      +  "example": 6,
      +  "type": "number"
      +}
    • addedInput schema / properties / body / properties / scheduledAt
      Added value: +{
      +  "description": "Timestamp when the post is scheduled to publish",
      +  "example": "2026-06-01T09:00:00.000Z",
      +  "format": "date-time",
      +  "type": "string"
      +}
    • addedInput schema / properties / body / properties / status / description
      Added value: +"Publication status of the blog post"
    • changedInput schema / properties / body / properties / status / enum
      Previous value: -[
      -  "DRAFT",
      -  "PUBLISHED",
      -  "SCHEDULED",
      -  "ARCHIVED"
      -]New value: +[
      +  "DRAFT",
      +  "PUBLISHED",
      +  "SCHEDULED",
      +  "ARCHIVED",
      +  "DELETED"
      +]
    • changedInput schema / properties / body / properties / status / example
      Previous value: -"PUBLISHED"New value: +"DRAFT"
    • removedInput schema / properties / body / properties / status / schema
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / body / properties / tags / description
      Added value: +"Tags applied to the blog post"
    • changedInput schema / properties / body / properties / tags / example
      Previous value: -[
      -  "blog",
      -  "seo"
      -]New value: +[
      +  "marketing",
      +  "seo"
      +]
    • addedInput schema / properties / body / properties / title / description
      Added value: +"Title of the blog post"
    • changedInput schema / properties / body / properties / title / example
      Previous value: -"Your blog title"New value: +"My Blog Post"
    • addedInput schema / properties / body / properties / tocStyle
      Added value: +{
      +  "description": "Table-of-contents style preference for the post",
      +  "example": "sidebar",
      +  "type": "string"
      +}
    • addedInput schema / properties / body / properties / type
      Added value: +{
      +  "description": "Post type marker (e.g., \"preview\")",
      +  "example": "preview",
      +  "type": "string"
      +}
    • addedInput schema / properties / body / properties / urlSlug / description
      Added value: +"URL-safe slug used in the blog post path"
    • changedInput schema / properties / body / properties / urlSlug / example
      Previous value: -"any-blog-post-url"New value: +"my-blog-post"
    • addedInput schema / properties / body / properties / wordCount / description
      Added value: +"Total word count of the blog post body"
    • changedInput schema / properties / body / properties / wordCount / example
      Previous value: -100New value: +1200
    • changedInput schema / properties / body / required
      Previous value: -[
      -  "title",
      -  "locationId",
      -  "blogId",
      -  "imageUrl",
      -  "description",
      -  "rawHTML",
      -  "status",
      -  "imageAltText",
      -  "categories",
      -  "author",
      -  "urlSlug",
      -  "publishedAt",
      -  "wordCount"
      -]New value: +[
      +  "locationId",
      +  "blogId",
      +  "rawHTML",
      +  "status"
      +]
    • addedInput schema / properties / body / title
      Added value: +"UpdateBlogPostParams"
    • changedInput schema / properties / postId / description
      Previous value: -"Path parameter (inferred from the URL template; the official spec omits its declaration)."New value: +"Identifier of the blog post to fetch"
    • addedInput schema / properties / postId / example
      Added value: +"66c381b38be80858b9af62b6"
  2. First observedv2.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare write/idempotent/non-destructive/openWorld, so the description earns credit for adding auth requirements and the version header that annotations do not cover. It still omits whether the body replaces the whole post or merges fields, and what happens to fields not supplied.

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?

Short and front-loaded: purpose first, then endpoint, then auth. Minor waste in restating the title twice and including the OpenAPI source file name, which has no decision value for an agent.

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

Completeness3/5

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

Auth and endpoint are covered and annotations handle the safety profile, but for a mutation tool whose body has four required fields the description never states that this is a full-replacement update or how omitted optional fields are treated. That omission matters for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so every parameter including the deeply nested body fields is documented in the schema. The description only echoes postId via the endpoint path and adds nothing about body semantics — baseline 3 is appropriate.

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?

States a specific verb+resource ("updates an existing blog post") plus scope ("for any given blog site"), which is enough to distinguish it from ghl_blog_post_create and ghl_blog_get_post_by_id. It does not explicitly name those siblings, so differentiation comes from the name/verb alone rather than from the text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives prerequisites (sub-account/location token, OAuth scope blogs/post-update.write) which imply the call context, but it never says when to use this versus creating a post or whether partial updates are allowed. Usage is inferable from the verb but not guided.

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