blogger-mcp-toolkit

blogger_posts_getByPath

Resolve public Blogger post links by retrieving the post via its URL path. Fetch the specific post details for any given path.

Instructions

Retrieve a single blog post by its URL path. Useful when resolving public blog links.

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

Input Schema

Name	Required	Description
`path`	Yes	URL path of the post, e.g. /2024/01/my-post.html
`view`	No	Access level with which to view the post.
`blogId`	Yes	The unique identifier of the blog.
`maxComments`	No	Maximum number of comments to fetch.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.3Aug 1, 2026

TDQS

A3.8/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the basic retrieval action and gives no information about permissions, return format, pagination, or potential side effects. This is a significant gap for a tool with no structured safety hints.

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, front-loaded with the action and followed by a relevant use case. No redundant information, making it extremely concise and to the point.

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?

Given the tool's simplicity and the fact that the schema covers all parameters exhaustively, the description provides the essential purpose and a typical use case. It does not mention optional parameters or return details, but these are either self-explanatory or covered by the schema, making this adequate for a straightforward retrieval tool.

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%, so the schema already documents all four parameters. The description adds minimal semantic value—it mentions 'path' as the key identifier, but that is already implied by the schema. It does not help disambiguate the optional 'view' or 'maxComments' parameters.

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 'Retrieve a single blog post by its URL path', using a specific verb with a clear resource and method. This distinguishes it from sibling tools like blogger_posts_get (which likely retrieves by ID) by emphasizing the path-based lookup.

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?

The phrase 'Useful when resolving public blog links' provides a clear context for when to use this tool. However, it does not explicitly mention alternatives or exclusions (e.g., when you have a post ID vs. a path), so it stops short of full guidance.

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