blogger-mcp-toolkit

blogger_comments_listByBlog

List all comments from a blog's posts to simplify global moderation. Filter by status, date, or pagination for targeted review.

Instructions

List comments across all posts in a blog. Useful for a global comment moderation view.

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>"
    },
    "name": "blogger_comments_listByBlog"
  }
}

Input Schema

Name	Required	Description
`blogId`	Yes	The unique identifier of the blog.
`status`	No	Statuses of the comments to retrieve.
`endDate`	No	End date (RFC 3339).
`pageToken`	No	Token for pagination.
`startDate`	No	Start date (RFC 3339).
`maxResults`	No	Maximum number of comments to return.
`fetchBodies`	No	Whether to fetch the full HTML bodies of the comments.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.3Aug 1, 2026

TDQS

A3.7/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 carry the burden of behavioral disclosure. It only states 'List' without mentioning pagination, default statuses, return format, or auth requirements. This is a significant gap for a tool with no annotation coverage.

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 two sentences, front-loaded with the core action and scope, and every word adds value. It is appropriately concise without missing essential 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?

Given the tool's moderate complexity and rich schema, the description covers purpose and use case but omits behavioral details like pagination or default filtering. With no output schema, it could mention the return shape, but 'List' partially implies it. Overall adequate but with notable 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?

Schema coverage is 100%, so the description need not restate parameter meanings. It adds a slight semantic cue by linking blogId to 'across all posts', but otherwise relies on the schema. 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 uses a specific verb ('List') and a clear resource ('comments across all posts in a blog'), distinguishing it from the sibling blogger_comments_list, which likely targets a single post. The scope is explicit and useful for moderation.

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?

It clearly suggests a use case ('global comment moderation view') that implies when to use this tool over per-post listing, but does not explicitly name alternatives or exclusions. The context is clear, yet lacks direct comparisons.

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