blogger-mcp-toolkit

blogger_posts_searchByLabel

Find and retrieve blog posts by label (tag). Filter by exact label, status, pagination, and summary-only mode.

Instructions

Quickly filter and retrieve posts for a blog by a specific label (tag).

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

Input Schema

Name	Required	Description
`label`	Yes	The exact label to filter posts by (e.g. 'Tech' or 'News').
`blogId`	Yes	The unique identifier of the blog.
`status`	No	Filter by post status.
`pageToken`	No	Pagination token.
`maxResults`	No	Maximum number of posts to fetch.
`summaryOnly`	No	If true, strips heavy HTML content from response items to return a lightweight summary.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.3Aug 1, 2026

TDQS

A3.6/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 disclose behavioral traits. It only states the basic function and does not mention pagination, status filtering, read-only nature, or response format. This is insufficient for a tool with multiple optional parameters.

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 one concise, front-loaded sentence that immediately states the action and target. No filler or redundant language is present.

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?

Despite the tool's moderate complexity (6 parameters, no output schema), the description lacks guidance on pagination, status filtering, or response contents. It does not compensate for the absence of an output schema, leaving the agent under-informed.

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 descriptions cover 100% of the parameters, so the schema already provides complete parameter semantics. The description adds no extra meaning beyond what the schema provides, warranting the baseline score of 3.

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 tool's function: filtering and retrieving posts by a specific label. This verb+resource+method structure distinguishes it from siblings like blogger_posts_list (all posts) and blogger_posts_search (content search).

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?

Provides clear context for when to use the tool (filter by label), but does not explicitly mention alternatives or when not to use it. The word 'quickly' hints at a lightweight operation but lacks direct comparison to sibling tools.

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