Skip to main content
Glama

merge-excel-range

Destructive

Combine cells in an Excel range into a single cell, or merge each row individually. Ideal for designing 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 include 'destructiveHint: true' which aligns with merging. The description adds that merging can be per row or entire range. However, it fails to disclose that merging typically keeps only the top-left cell's content, which is a critical behavioral detail for a destructive operation.

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 is reasonably short but includes a redundant first line 'Invoke action merge'. The tip is helpful and front-loaded, but the structure could be improved by removing the repetitive first sentence.

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

Completeness2/5

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

Given the tool has 7 parameters (5 required) and no output schema, the description omits important context such as the effect on existing cell content (data loss), return value, and side effects. It also does not explain the result of the merge action.

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

Parameters3/5

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

Schema description coverage is 86%, and the schema already provides basic descriptions for path parameters. The description adds meaning to the 'across' parameter inside 'body', but does not enrich understanding of other parameters like 'address' (range address) or the required identifiers.

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 merges cells in a given Excel range into a single cell, with an option to merge each row separately. This clearly distinguishes it from other Excel range tools like format or sort, but does not explicitly differentiate from the sibling 'unmerge-excel-range'.

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 guidance on using the 'across' parameter and suggests use cases like building headers and report layouts. However, it does not mention when not to use this tool or suggest alternatives (e.g., unmerge-excel-range).

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