blogger-mcp-toolkit

blogger_comments_delete

Permanently delete a comment from a Blogger post using blog, post, and comment IDs.

Instructions

Permanently delete a comment from a 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>",
      "commentId": "<commentId>"
    },
    "name": "blogger_comments_delete"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.3Aug 1, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations provided, the description carries the burden of disclosing safety-critical behavior. 'Permanently delete' clearly communicates irreversibility, which is a significant behavioral trait beyond the tool name. It does not mention auth requirements or side effects, but the core destructive nature is explicit.

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 sentence that front-loads the action and permanence. Every word contributes, with no fluff or repetition.

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 delete tool with fully documented parameters and no output schema, the description is largely sufficient. However, given multiple comment-related siblings, a note on when to choose delete over removeContent or markAsSpam would enhance completeness slightly.

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?

Schema description coverage is 100%, with each parameter (blogId, postId, commentId) clearly described in the schema. The description adds no additional parameter context, so it meets the baseline but does not exceed it.

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 'Permanently delete a comment from a post' uses a specific verb (delete), names the resource (comment), and specifies scope (from a post). It clearly distinguishes from sibling tools like blogger_comments_approve or blogger_comments_removeContent by emphasizing permanence.

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 usage for permanent deletion, but it does not explicitly contrast with similar comment moderation tools such as removeContent or markAsSpam. No when-to-use or when-not-to-use guidance is provided, leaving the agent to infer from tool names.

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