Skip to main content
Glama

insert_paragraph

Insert a new paragraph after a specified paragraph in a Word document, with optional heading or normal style.

Instructions

Insert a new paragraph after the paragraph with the given paraId.

Args: after_para_id: paraId of the paragraph to insert after. text: Text content for the new paragraph. style: Optional paragraph style name (e.g., "Heading1", "Normal").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
after_para_idYes
textYes
styleNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description discloses the action and all parameters clearly. No annotations are provided, so the description carries the burden. It does not discuss error handling or return values, but for a simple insertion, it is adequately transparent.

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 very concise with two sentences and a structured argument list. Every sentence adds value with no redundant information.

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 tool with 3 parameters and an output schema, the description covers the core purpose and parameters. It lacks error handling details, but overall is complete enough for an agent to use 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 0%, so the description must add meaning. It explains each parameter with examples (e.g., 'Heading1' for style), which significantly aids understanding beyond the schema's bare titles.

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 inserts a new paragraph after a specified paragraph by paraId. This specific action distinguishes it from other insertion tools like insert_text.

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 implies usage when inserting a paragraph after an existing one, and distinguishes from siblings like insert_text. However, it lacks explicit exclusions or alternative tool guidance.

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/SecurityRonin/docx-mcp'

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