Skip to main content
Glama

neuron

by io.github.conquext

Update Blog Post

neuron_update_blog_post
Idempotent

Update an existing blog post's content, metadata, status, or SEO fields. Only provided fields are changed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUnique identifier (UUID) of the blog post to update
tagsNoReplace the post's tags with this list of tag names (created if missing). Empty array clears all tags; omit to leave tags unchanged.
titleNoNew title for the blog post
blocksNoStructured layout blocks, rendered top-to-bottom as styled components. Each block is an object with a `type` and its fields: - hero: { type:'hero', title, kicker?, subtitle?, imageUrl?, align?:'left'|'center', ctaLabel?, ctaHref? } - richText: { type:'richText', markdown } (full GFM markdown) - callout: { type:'callout', variant:'info'|'tip'|'warning'|'success'|'danger', title?, markdown } - columns: { type:'columns', ratio?:'1-1'|'1-2'|'2-1', columns:[ [block,...], [block,...] ] } (exactly 2 columns of leaf blocks; no nested columns) - codeCard: { type:'codeCard', language?, filename?, code } - imageGrid: { type:'imageGrid', columns?:1|2|3|4, images:[{ url, alt?, caption? }] } - quote: { type:'quote', quote, attribution? } - embed: { type:'embed', provider:'youtube'|'loom'|'vimeo'|'generic', url, title? } (paste the normal share URL) - cta: { type:'cta', headline, body?, buttonLabel, buttonHref, secondaryLabel?, secondaryHref?, accent?:'#hex' } - divider: { type:'divider' } - html: { type:'html', html, sandboxed?, height? } (custom HTML. Default is sanitized + indexable, no scripts. Set sandboxed:true to run scripts inside an isolated iframe — NOT indexed by search.) Build magazine-style posts by composing these, e.g. a hero, then richText, then a columns block, a callout, a codeCard, and a closing cta. Pass null to clear blocks and revert to the markdown `content`. Omit to leave existing blocks unchanged.
statusNoNew publication status for the post
contentNoNew markdown body (GFM + inline raw HTML). Supports ![alt](url), <video>, <iframe> embeds, <details>/<summary>, <mark>, <kbd>.
excerptNoNew short summary or preview text
seoTitleNoNew custom SEO title override
seoKeywordsNoNew list of SEO keywords
coverImageUrlNoNew URL for the cover image
seoDescriptionNoNew meta description for search engines

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • addedInput schema / properties / blocks
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Structured layout blocks, rendered top-to-bottom as styled components. Each block is an object with a `type` and its fields:\n- hero: { type:'hero', title, kicker?, subtitle?, imageUrl?, align?:'left'|'center', ctaLabel?, ctaHref? }\n- richText: { type:'richText', markdown }  (full GFM markdown)\n- callout: { type:'callout', variant:'info'|'tip'|'warning'|'success'|'danger', title?, markdown }\n- columns: { type:'columns', ratio?:'1-1'|'1-2'|'2-1', columns:[ [block,...], [block,...] ] }  (exactly 2 columns of leaf blocks; no nested columns)\n- codeCard: { type:'codeCard', language?, filename?, code }\n- imageGrid: { type:'imageGrid', columns?:1|2|3|4, images:[{ url, alt?, caption? }] }\n- quote: { type:'quote', quote, attribution? }\n- embed: { type:'embed', provider:'youtube'|'loom'|'vimeo'|'generic', url, title? }  (paste the normal share URL)\n- cta: { type:'cta', headline, body?, buttonLabel, buttonHref, secondaryLabel?, secondaryHref?, accent?:'#hex' }\n- divider: { type:'divider' }\n- html: { type:'html', html, sandboxed?, height? }  (custom HTML. Default is sanitized + indexable, no scripts. Set sandboxed:true to run scripts inside an isolated iframe — NOT indexed by search.)\nBuild magazine-style posts by composing these, e.g. a hero, then richText, then a columns block, a callout, a codeCard, and a closing cta.\n\nPass null to clear blocks and revert to the markdown `content`. Omit to leave existing blocks unchanged."
+}
    • changedInput schema / properties / content / description
      Previous value: -"New body content in markdown format. Supports raw HTML inline via rehype-raw: images/GIFs via ![alt](url), videos via <video>, YouTube/Loom embeds via <iframe>, collapsible sections via <details>/<summary>, plus <mark>, <kbd>, <abbr>."New value: +"New markdown body (GFM + inline raw HTML). Supports ![alt](url), <video>, <iframe> embeds, <details>/<summary>, <mark>, <kbd>."
    • addedInput schema / properties / tags
      Added value: +{
+  "description": "Replace the post's tags with this list of tag names (created if missing). Empty array clears all tags; omit to leave tags unchanged.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / content / description
      Previous value: -"New body content in markdown format"New value: +"New body content in markdown format. Supports raw HTML inline via rehype-raw: images/GIFs via ![alt](url), videos via <video>, YouTube/Loom embeds via <iframe>, collapsible sections via <details>/<summary>, plus <mark>, <kbd>, <abbr>."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover idempotency and non-destructiveness, so the description does not need to repeat those. It adds a useful behavioral detail: omitted fields are left unchanged, which clarifies the update semantics beyond what the annotations alone convey. No contradiction exists.

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

Conciseness5/5

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

The description is two short sentences with no filler. The action and resource are front-loaded, and the most important behavioral constraint is stated immediately after the core purpose.

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?

The rich schema and annotations cover parameter semantics and safety behavior, so the description does not need to repeat them. The main gaps are the lack of return-value details and no explicit guidance for choosing between this and publish_blog_post, but these do not prevent correct invocation for standard updates.

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 description coverage is 100%, so parameter details are already well documented. The description still adds value by stating globally that only provided fields are changed, which applies uniformly to all optional parameters and reinforces the partial-update model.

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?

The description clearly states that the tool updates an existing blog post’s content, metadata, status, or SEO fields, making the verb and resource explicit. The word 'existing' differentiates it from create/delete tools, and the specific field categories give a clear sense of scope beyond the tool name.

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 implies partial updates by saying 'Only provided fields are changed,' but it does not explicitly say when to prefer this tool over siblings like create_blog_post, delete_blog_post, or publish_blog_post. The overlap with publish_blog_post through the status field is not addressed, leaving some selection ambiguity.

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

All neuron toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation3/5

Most tools are clearly separated by resource type, but there is meaningful overlap in messaging entry points (send_message, send_whatsapp, compose_message, bot_api_send) and contact ingestion/sync tools (import_contacts, populate_contacts, sync_whatsapp_contacts). The descriptions help disambiguate, but with 309 tools an agent will frequently need to read closely to pick the right one.

Naming Consistency4/5

The overwhelming majority of tools follow a consistent verb_noun snake_case pattern: create_*, get_*, list_*, update_*, delete_*. Minor deviations like sales_stats, lead_stats, wallet_balance, and whoami break the pattern slightly, but overall naming is highly predictable.

Tool Count1/5

309 tools is an extreme count for any MCP server, even a broad platform. This creates significant cognitive load and navigation overhead for agents, and far exceeds the well-scoped 3-15 tool range where coherence is strongest.

Completeness4/5

The tool surface is remarkably comprehensive across bots, contacts, campaigns, flows, knowledge bases, personas, marketplace, wallet, and products. Minor gaps exist — lead sources lack update/delete tools, and there is no single get_task or get_webhook alongside their list/update/delete counterparts — but these are workable gaps rather than dead ends.

Resources