blogger-mcp-toolkit

blogger_posts_publish

Publish draft Blogger posts immediately or schedule them for future publication using the Blogger API.

Instructions

Publish a draft blog post, either immediately or scheduled for the future.

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_publish"
  }
}

Input Schema

Name	Required	Description
`blogId`	Yes	The unique identifier of the blog.
`postId`	Yes	The unique identifier of the post to publish.
`publishDate`	No	ISO 8601 date-time string to schedule publishing for the future.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.3Aug 1, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It reveals the two behavioral modes (immediate vs. scheduled) but does not mention the post's status change, reversibility, or failure conditions. The scheduling option adds some value beyond the schema.

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 13-word sentence that directly states the action and its two variants, with zero redundancy. It is front-loaded and efficiently communicates the core purpose.

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?

For a 3-parameter publish tool with no output schema or annotations, the description covers the essential purpose and the two modes, but omits the return value, error conditions, and irreversibility. It is adequate for a simple action but has clear gaps.

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 input schema has 100% coverage with descriptions for all three parameters, so the baseline is 3. The description's mention of 'scheduled for the future' aligns with the publishDate parameter but adds no new information beyond what the schema already provides.

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 the specific verb 'publish' with the resource 'blog post' and explicitly distinguishes between immediate and scheduled publishing. This clearly differentiates it from sibling tools like revert, delete, and update, which have distinct purposes.

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?

The description implies the use case: publish a draft post, either now or later. However, it does not explicitly state when not to use this tool (e.g., for updating existing content) or mention any prerequisites like ownership or required permissions.

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