blogger-mcp-toolkit

blogger_users_get

Retrieve a Blogger user's profile information, including user ID, display name, profile URL, and location. Use 'self' to fetch the authenticated user's details.

Instructions

Retrieve a user's Blogger profile information. Returns details like user ID, display name, profile URL, and location.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "blogger_users_get"
  }
}

Input Schema

Name	Required	Description	Default
`userId`	No	The ID of the user to retrieve, or "self" for the currently authenticated user.	self

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.3Aug 1, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It mentions the tool returns user details (ID, name, URL, location), which gives some insight into behavior, but it does not state whether authentication is required, that it is a read-only operation, or any other operational constraints.

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 concise sentences, front-loaded with the primary action and then elaborating on return details. Every word earns its place with no redundancy.

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 get-profile tool with one optional parameter and no output schema, the description adequately conveys purpose and returns. It doesn't need to detail return values extensively, though it could briefly note the parameter default (already in schema). Overall, it is sufficient.

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 schema already provides full coverage for the single userId parameter, including its default value and meaning. The description adds no additional parameter semantics beyond what the schema states, so baseline 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 clearly states the tool retrieves a user's Blogger profile information, using the specific verb 'Retrieve' and naming the resource. It distinguishes itself from sibling tools, as no other tool handles user profile retrieval.

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 description clearly implies when to use this tool: when you need a Blogger user's profile details. It doesn't explicitly exclude alternatives, but no sibling tool serves the same purpose, making the use case clear.

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