blogger-mcp-toolkit

blogger_posts_search

Search blog posts by query string within a specified blog. Optionally, summary mode provides lightweight results without heavy HTML content.

Instructions

Search across a blog's posts using a text query string, with optional lightweight summary mode.

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

Input Schema

Name	Required	Description
`q`	Yes	Search query string to search for in posts.
`blogId`	Yes	The unique identifier of the blog.
`orderBy`	No	Sort order for the search results.
`fetchBodies`	No	Whether to fetch full post bodies in the results.
`summaryOnly`	No	If true, strips heavy HTML content from search result items.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.3Aug 1, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full burden for behavioral disclosure. It mentions 'optional lightweight summary mode' but does not state whether the operation is read-only, describe pagination, or address authentication. The description adds some context but lacks important behavioral details.

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, well-structured sentence that front-loads the action ('Search') and resource ('a blog's posts'). It avoids redundant wording and is appropriately concise for its 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?

Although the description is clear about the core function, it lacks details about return structure, pagination, or how it compares to searchByLabel. With no output schema or annotations, the description should cover these gaps but only partially does so.

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 100% coverage of parameter descriptions. The description's mention of 'text query string' and 'summary mode' aligns with q and summaryOnly but adds no new semantics beyond what the schema already documents. Baseline 3 applies because schema is fully self-explanatory.

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: searching across a blog's posts using a text query string. It distinguishes itself from siblings like blogger_posts_list (list all posts) and blogger_posts_searchByLabel (search by label) by emphasizing text-based search.

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 when text-based search is needed, but it does not explicitly provide alternatives or exclusions. No comparison to sibling tools like searchByLabel or list is offered, leaving the agent to infer when this tool is the right choice.

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