blogger-mcp-toolkit

blogger_posts_patch

Partially update a Google Blogger post by changing only the fields you specify, such as title, content, labels, or publish status.

Instructions

Perform a partial update of a blog post, updating only the provided fields.

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

Input Schema

Name	Required	Description
`title`	No	The new title of the post (optional).
`blogId`	Yes	The unique identifier of the blog.
`labels`	No	The new list of labels (optional).
`postId`	Yes	The unique identifier of the post to update.
`revert`	No	Whether to revert the post to draft status.
`content`	No	The new HTML content of the post (optional).
`publish`	No	Whether to publish the post upon updating.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.3Aug 1, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions partial-update behavior but omits side effects of the 'publish' and 'revert' parameters, authentication requirements, rate limits, or response format. This is a significant gap for a mutation tool.

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, front-loaded sentence with no filler. It directly states the purpose and key behavior, achieving maximum conciseness.

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

Completeness2/5

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

Given the tool's complexity (7 parameters, no output schema, no annotations), the one-sentence description is insufficient. It does not explain return values, the effects of 'publish'/'revert', prerequisites, or relationships to sibling tools like blogger_posts_publish and blogger_posts_revert.

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 provides complete descriptions for all 7 parameters (100% coverage), so the description need not add parameter details. The phrase 'only the provided fields' reinforces the optional nature of most parameters, which is already evident from the schema. Baseline score of 3 applies.

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 the action ('Perform a partial update') and the resource ('a blog post'). The phrase 'partial update' and 'only the provided fields' effectively distinguishes this tool from the full update tool (blogger_posts_update) and other sibling tools.

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 the tool is used when only specific fields need updating, but it does not explicitly state when not to use it or name alternatives. No exclusions or alternative tool references are provided, so the guidance is purely implicit.

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