blogger-mcp-toolkit

blogger_posts_revert

Revert a published Blogger post back to draft status. Use when you need to undo a publication or make edits before republishing.

Instructions

Revert a published blog post back to a draft.

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": {
      "blogId": "<blogId>",
      "postId": "<postId>"
    },
    "name": "blogger_posts_revert"
  }
}

Input Schema

Name	Required	Description	Default
`blogId`	Yes	The unique identifier of the blog.
`postId`	Yes	The unique identifier of the post to revert.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.3Aug 1, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the state change (published to draft) but omits side effects, permissions required, idempotency, or behavior when the post is not published.

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 a single concise sentence that immediately conveys the tool's action and resource. No filler or redundancy, making it highly efficient.

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?

The tool is simple with well-documented parameters, but the description lacks behavioral context (e.g., error cases, prerequisites). It is adequate for basic usage but not fully complete for a mutation tool without annotations.

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?

The schema already provides complete descriptions for both parameters (blogId, postId) with 100% coverage. The description adds no additional parameter meaning, so the baseline of 3 is appropriate.

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 uses a specific verb ('revert') and resource ('published blog post back to a draft'), clearly distinguishing it from sibling tools like 'publish' (which does the opposite) or 'delete' (which removes entirely).

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

Usage Guidelines2/5

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

The description provides no explicit guidance on when to use this tool versus alternatives like publish or delete. The intended use is implied by the name, but no context, prerequisites, or exclusions are stated.

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