KitchenSink4Word

Overview Schema Source Related Servers Discussions Admin

Insert Paragraphs

insert_paragraphs

Insert paragraphs into Word docs at any location, with formatting, headings, and live editing. Supports tracked changes and auto-backup.

Instructions

Insert paragraphs (items {text, style?, formatting?, heading_level?, paragraph_format?}) at a location object (omitted = document end). heading_level 1-9 makes it a heading (1 = outline 0). paragraph_format takes set_paragraph_format keys; it and inherit_format/copy_format_from (clone neighbor formatting minus outline level) are file mode only. track records insertions by author. Auto-backup; atomic save. Open documents edit live; a stale text-selector target refuses: save in Word, retry. Batches: apply_edits.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`live`	No	auto: file or live; force: live; off: refuse	auto
`track`	No
`author`	No		Claude
`backup`	No
`location`	No
`file_path`	Yes
`paragraphs`	Yes
`inherit_format`	No
`copy_format_from`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.2.1Sep 24, 2026
- addedInput schema / properties / live / description
```
Added value: +"auto: file or live; force: live; off: refuse"
```
- addedInput schema / properties / live / enum
```
Added value: +[
+  "auto",
+  "force",
+  "off"
+]
```

Changed5 schema fields changedv2.0.0Sep 4, 2026

removedInput schema / properties / after_anchor

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}

removedInput schema / properties / after_index

Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}

removedInput schema / properties / at_end

Removed value: -{
-  "default": false,
-  "type": "boolean"
-}

removedInput schema / properties / before_index

Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}

addedInput schema / properties / location

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

Changed3 schema fields changedv1.6.1Aug 31, 2026

addedInput schema / properties / copy_format_from

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / inherit_format

Added value: +{
+  "default": false,
+  "type": "boolean"
+}

addedInput schema / properties / live

Added value: +{
+  "default": "auto",
+  "type": "string"
+}

First observedv1.2.1Aug 27, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations are minimal (only flags), so the description carries the behavioral burden. It discloses auto-backup, atomic save, live editing behavior, stale target refusal with remediation, and track/author recording. This goes well beyond annotations and gives an agent concrete expectations about side effects and failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but efficient, using semicolons to pack multiple facts. It leads with the core action and item structure, then layers on constraints and behaviors. It's not overly verbose, though the density might require careful reading.

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 complex tool with 9 parameters and low schema coverage, the description covers most essential aspects: location, paragraph structure, heading behavior, formatting options, track/author, backup, live editing, and batch alternative. Minor ambiguities remain (e.g., exact meaning of 'stale text-selector target'), but overall it provides enough to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 11%, so the description must compensate. It explains the structure of paragraphs items (text, style, formatting, heading_level, paragraph_format), semantics of heading_level (1-9, 1=outline 0), paragraph_format keys, inherit_format/copy_format_from behavior, track and author, and location default. Nearly all parameters are meaningfully described, far exceeding schema coverage.

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 clearly states the tool inserts paragraphs, and describes the item structure and location parameter. It doesn't explicitly differentiate from sibling insert tools (e.g., insert_list, insert_break), but the purpose is unambiguous given the resource (paragraphs) and action (insert).

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?

It provides clear context: location omitted means document end, file-mode-only constraints for certain features, and it explicitly points to apply_edits for batch operations. It doesn't name sibling insert tools as alternatives, but the batch guidance and live-editing caveats give practical when-to-use information.

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