OrgLines

Blog: Update post

blog_update_post

Destructive

Edit a blog post: title, text (replaces the whole body), excerpt, tags, SEO title/description. Does not change whether it is published — use blog_publish_post for that. Runs propose→confirm. CONFIRMATION: this tool is PROPOSED, never performed directly. You get status='confirmation_required' with an action_id and a plan_token, and the write happens only after confirm_action.

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

Input Schema

Name	Required	Description
`tags`	No
`text`	No	Article text. Paragraphs separated by a blank line; a line starting with '## ' or '### ' is a heading; lines starting with '- ' form a list. Inline bold, italic and [label](https://url) are kept.
`title`	No
`excerpt`	No
`post_id`	Yes
`seo_title`	No
`seo_description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing that text replaces the entire body, that the call runs propose→confirm, and that it is never performed directly — returning status='confirmation_required' with an action_id and plan_token before the write occurs via confirm_action. This is exactly the kind of behavioral context annotations cannot convey, and it is consistent with destructiveHint=true.

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?

Front-loaded with what it edits, then the publish exclusion, then the confirmation protocol. Every sentence carries information the agent needs; nothing is redundant with the schema or annotations.

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?

A destructive mutation with no output schema, yet the description explains the return contract (status, action_id, plan_token) and the follow-up tool. Only the required post_id parameter and any ordering/precondition details are left implicit.

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 only 14%, so the description must compensate, and it largely does by naming six of the seven parameters and clarifying that text overwrites the whole body rather than appending. It does not explain post_id (the required parameter), which is the one remaining 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 a specific verb and resource ('Edit a blog post') and enumerates the editable fields (title, text, excerpt, tags, SEO title/description). It explicitly draws the boundary against blog_publish_post, so an agent can distinguish it from the closest sibling without opening either schema.

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?

Provides an explicit exclusion and alternative: publishing state is not changed here, use blog_publish_post for that. It does not discuss when to use this versus blog_create_draft or blog_get_post, but the primary ambiguity for an update tool is handled clearly.

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

All OrgLines tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?