blogger-mcp-toolkit

blogger_posts_delete

Permanently delete a blog post by supplying the blog ID and post ID. Removes content from Google Blogger via the API.

Instructions

Permanently delete a blog post.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.3Aug 1, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Without annotations, the description carries the burden of disclosing behavioral traits. It explicitly mentions 'permanently delete', which communicates that the operation is destructive and irreversible. However, it does not disclose any side effects (e.g., whether comments are also deleted) or required permissions, so it is adequate but not rich.

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, tightly worded sentence with no redundant words. 'Permanently' adds meaningful nuance, and the structure is front-loaded, making it concise and effective.

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?

For a simple destructive operation with two fully documented parameters and no output schema, the description is nearly complete. It conveys the tool's purpose and irreversibility, though it could benefit from a brief note on when to use deletion versus other post-modification tools.

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 provides clear descriptions for both blogId and postId, achieving 100% coverage. The description adds no additional parameter-specific semantics, so the baseline score 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 clearly states the action with the specific verb 'delete' and the resource 'blog post', and the word 'permanently' adds key information about irreversibility, distinguishing it from other post operations like publish, update, or revert.

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 guidance on when to use this tool versus alternatives. It does not mention prerequisites, scenarios where deletion is preferred over other operations, or any exclusions, leaving usage entirely to inference.

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