Skip to main content
Glama

merge-excel-range

Destructive

Merge cells in an Excel range into one cell or merge each row separately for styled headers and report layouts.

Instructions

Invoke action merge

💡 TIP: Merge the cells in the given range into a single cell. Body: { across: false } merges the entire range into one cell; { across: true } merges each row separately. Useful for building styled headers, banner rows, and report layouts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
driveIdYesPath parameter: driveId
driveItemIdYesPath parameter: driveItemId
workbookWorksheetIdYesPath parameter: workbookWorksheetId
addressYesPath parameter: address
includeHeadersNoInclude response headers (including ETag) in the response metadata
excludeResponseNoExclude the full response body and only return success or failure indication
Behavior3/5

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

Annotations already indicate destructive hint. The description adds behavior details for the across parameter (merge whole range vs. per row). However, it does not disclose potential data loss when merging cells with content, nor does it address openWorldHint implications.

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

Conciseness3/5

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

The description starts with a generic 'Invoke action merge' that is unnecessary. The rest is concise and well-structured with a tip, but the opening sentence wastes space.

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 mutation tool with no output schema and moderate complexity, the description covers core behavior and use cases but lacks details on data loss, error handling, and prerequisites. It is adequate but not thorough.

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 has high coverage (86%) with basic parameter descriptions. The tool description adds significant value by explaining the 'body.across' parameter's effect, which is not fully detailed in the schema. It does not elaborate on the path parameters, but those are standard.

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 that the tool merges cells in a given range, with specific behavior based on the 'across' parameter. It distinguishes from siblings like unmerge-excel-range. The tip reinforces the purpose.

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 provides use cases (building headers, banners, reports), but does not explicitly state when not to use it or compare to alternative tools like format-excel-range or clear-excel-range. Usage context is implied.

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/Softeria/ms-365-mcp-server'

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