Skip to main content
Glama

insert_paragraphs

Insert paragraphs into a Word document at a precise location—after or before an index or unique anchor text, or at the end—with optional format cloning and tracked changes.

Instructions

Insert paragraphs ({text, style?, formatting?}) at ONE position: after_index | before_index | after_anchor | at_end. Anchors match a paragraph's PLAIN text (write '&', never the XML entity '&') and must be unique; heading text recurs in body prose, so prefer index addressing for structural work. On a fresh document, index 0 addresses the implicit empty paragraph. inherit_format=True clones the anchor paragraph's direct formatting onto the inserted paragraphs (a reference entry matches its neighbors' hanging indent and font in one call); with before_index/at_end use copy_format_from= instead (mutually exclusive). Explicit per-item style/formatting wins; track records tracked insertions by author. Format cloning is file-mode only. Auto-backup in file mode: prev/anchor slots in .ks4w-backups (backup=False skips rotation only); atomic validated save. Documents open in Word are edited live.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
liveNoauto
trackNo
at_endNo
authorNoClaude
backupNo
file_pathYes
paragraphsYes
after_indexNo
after_anchorNo
before_indexNo
inherit_formatNo
copy_format_fromNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations available, the description carries full responsibility for behavioral disclosure. It reveals key side effects: track changes recording, file-mode-only format cloning, auto-backup behavior, atomic validated saves, and live editing of Word-open documents. This goes well beyond a simple mutation statement.

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 and front-loaded, leading with the core operation and position modes. It is long, but nearly every clause adds necessary detail for a 12-parameter tool; a bit of restructuring into clearer lists would improve scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex insertion tool with no annotations and no schema parameter descriptions, the description is remarkably complete. It covers edge cases, parameter interactions, file-mode constraints, and persistence/backup behavior. The presence of an output schema means return-value details are not required here.

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 0%, so the description must compensate, and it does thoroughly. It explains position parameters, the meaning of inherit_format vs copy_format_from and their mutual exclusivity, track/author behavior, backup rotation semantics, and per-item style precedence.

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 specifies a clear action and resource: inserting paragraphs at one of four explicit positions. The mention of position modes and anchor/index semantics distinguishes it from many sibling insert tools.

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 strong within-tool guidance: anchors must be unique, index addressing is preferred for structural work due to recurring heading text, and fresh documents have an implicit empty paragraph at index 0. It does not name alternative sibling tools explicitly, so it stops short of full cross-tool routing.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nometalalchemist/KitchenSink4Word'

If you have feedback or need assistance with the MCP directory API, please join our Discord server