blogger-mcp-toolkit

blogger_pages_insert

Create a new static page on a blog by supplying the title and HTML content, with optional draft mode before publishing.

Instructions

Create a new static page for a blog with the specified title and HTML content.

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_pages_insert"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	The title of the new page.
`blogId`	Yes	The unique identifier of the blog.
`content`	Yes	The full HTML content of the new page (Markdown wrappers will be automatically cleaned).
`isDraft`	No	Whether to create the page as a draft (true) or published (false).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.3Aug 1, 2026

TDQS

A3.7/5.0

Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'Create' without mentioning publication defaults, return values, permissions, or side effects. The schema notes isDraft default but the description adds no behavioral context beyond the action itself.

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?

A single, clear, front-loaded sentence with no redundant wording. It earns its place.

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?

The schema fully documents parameters, but with no annotations and no output schema, the description leaves gaps about return values and post-create behavior. It is adequate for a simple create operation but not fully complete.

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 baseline is 3. The description's mention of 'title and HTML content' merely echoes the schema and does not add further semantic value.

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 action 'Create a new static page' with specific details about title and HTML content. It distinguishes from sibling tools like blogger_posts_insert by specifying 'static page' and from page update/delete tools through the verb 'create'.

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 term 'static page' provides clear context that this tool is for Blogger pages, differentiating it from posts. However, it does not explicitly mention when not to use it or name alternatives, so it falls short of a 5.

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