Skip to main content
Glama

format-excel-range

Destructive

Update Excel range formatting: set alignment, text wrapping, column width, and row height for a specified range address.

Instructions

Update the navigation property format in drives

💡 TIP: Apply rangeFormat properties to a specific range. Required path param 'address' (e.g. 'A1:E5' or 'Sheet1!A1:E5'). Body: { horizontalAlignment, verticalAlignment, wrapText, columnWidth, rowHeight }. Note: font, fill, and borders are sub-resources on rangeFormat — set them via /format/font, /format/fill, and /format/borders/{sideIndex} respectively, not on this endpoint.

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
Behavior4/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false. The description adds context by naming the supported properties and pointing to sub-resources for font/fill/borders. It does not explicitly state if unspecified properties reset, but the destructive hint implies overwrite is possible.

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 concise, with a main sentence and a TIP. It could be better structured (e.g., bullet points) but contains no fluff and front-loads the essential purpose.

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?

Given no output schema and 7 parameters, the description covers the core functionality (range address, body properties) and clarifies sub-resources. It does not explain the effect of 'includeHeaders' or 'excludeResponse' but these are common parameters. The update behavior (partial vs full) is implicit.

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 86% coverage, but the description adds value by providing an example for the 'address' parameter (e.g., 'A1:E5' or 'Sheet1!A1:E5') and listing the body properties. This extends beyond the schema's terse description for 'address'.

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 updates formatting properties on an Excel range, with specific properties listed (horizontalAlignment, verticalAlignment, wrapText, columnWidth, rowHeight). It distinguishes itself from siblings by clarifying that font, fill, and borders are handled via separate endpoints.

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 includes a TIP that explains how to apply the format and explicitly excludes font, fill, and borders, guiding the agent not to use this endpoint for those. However, it does not explicitly compare with other sibling tools like 'clear-excel-range' or 'sort-excel-range', though the purpose remains distinct.

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