ms-365-mcp-server

insert-excel-range

insert-excel-range

Destructive

Insert blank cells into an Excel worksheet at a specified range, shifting existing content down or right.

Instructions

Insert an Excel range.

💡 TIP: Insert blank cells at the given range, shifting existing content. Body: { shift: 'Down' } or { shift: 'Right' }. Use 'Down' to insert blank rows above existing data.

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": {
      "body": "<body>",
      "driveId": "<driveId>",
      "driveItemId": "<driveItemId>",
      "workbookWorksheetId": "<workbookWorksheetId>",
      "address": "<address>"
    },
    "name": "insert-excel-range"
  }
}

Input Schema

Name	Required	Description
`body`	Yes
`address`	Yes	Value for the 'address' path segment.
`confirm`	No	For destructive operations when the confirm gate is enabled (MS365_MCP_REQUIRE_CONFIRM=true; off by default). Set to true only after the user has explicitly approved this action. When the gate is on, calls without confirm: true return { error: "confirmation_required" } without touching user data.
`driveId`	Yes	Value for the 'driveId' path segment. Pass it under the name 'driveId', not as 'id'. Use the 'id' field of the drive object as returned by Microsoft Graph.
`driveItemId`	Yes	Value for the 'driveItemId' path segment. Pass it under the name 'driveItemId', not as 'id'. Use the 'id' field of the drive item object as returned by Microsoft Graph.
`includeHeaders`	No	Include response headers (including ETag) in the response metadata
`excludeResponse`	No	Exclude the full response body and only return success or failure indication
`workbookWorksheetId`	Yes	Value for the 'workbookWorksheetId' path segment. Pass it under the name 'workbookWorksheetId', not as 'id'. Use the 'id' field of the workbook worksheet object as returned by Microsoft Graph.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0-developmentAug 24, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already mark this as destructive (destructiveHint: true), so the description does not need to reiterate that. It adds useful behavior details: inserts blank cells at the given range and shifts existing content. It does not mention side effects like formatting or undo, but given annotation coverage, it provides sufficient extra 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 concise, using two sentences plus a tip. It is front-loaded with the main action and immediately provides the key parameter direction. There is no fluff.

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?

For a destructive operation with no output schema and multiple path parameters, the description is lean but adequate. It explains the core effect and gives a tip for the shift parameter. It does not discuss response format, confirmation requirements, or error cases, but these are not critical given the schema and annotations. It could be slightly more thorough about what 'range' means in terms of the address parameter.

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

Parameters4/5

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

The schema already describes all parameters with high coverage (88%). The description adds specific guidance for the 'shift' parameter by showing valid values ('Down' or 'Right') and their effect, which is not present in the schema. This enhances parameter understanding beyond the basic type definition.

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 action: inserting blank cells at the given range and shifting existing content. It distinguishes from siblings like delete-excel-range or clear-excel-range by explicitly describing the insertion-and-shift behavior. The verb 'insert' is specific, and the tip clarifies the exact effect, though it does not mention the address parameter explicitly.

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

Usage Guidelines3/5

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

The description gives one practical usage hint: using 'Down' to insert rows above existing data. However, it does not explain when to choose this tool over alternatives like delete-excel-range or clear-excel-range, nor does it mention any prerequisites or context. The guidance is minimal and focuses on the shift direction rather than overall usage.

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

Deploy Server