blogger-mcp-toolkit

blogger_posts_insert

Create a new blog post with title, HTML content, labels, and draft status. Publish immediately or save as draft.

Instructions

Create a new blog post.

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>",
      "title": "<title>",
      "content": "<content>"
    },
    "name": "blogger_posts_insert"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	Title of the new post.
`blogId`	Yes	The unique identifier of the blog.
`labels`	No	List of labels (tags) to apply to the post.
`content`	Yes	Full HTML content of the new post (Markdown wrappers will be automatically cleaned).
`isDraft`	No	Whether to create the post as a draft (true) or publish it immediately (false).
`customMetaData`	No	Custom metadata string for the post.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.3Aug 1, 2026

TDQS

C2.9/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 behaviors. It only says 'create' implies mutation but does not mention authentication, immediate publishing, or side effects. The schema covers isDraft, but description adds no behavioral context.

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, focused sentence with zero redundancy. It is concise and front-loaded.

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?

With no output schema and no annotations, the description should provide context about return values, draft/publish behavior, and errors. It does not, leaving significant gaps for a tool with 6 parameters.

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 fully documents parameters. The description adds no additional parameter information, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Create') and resource ('a new blog post'), clearly indicating the operation. However, it does not distinguish this from sibling tools like blogger_posts_update or blogger_pages_insert, so it lacks explicit differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance about when to use this tool vs alternatives. It simply states what it does, without mentioning publication state, draft handling, or exclusions.

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