Skip to main content
Glama

update-excel-range

Destructive

Set cell values, formulas, or number format on any Excel range, supporting append, update, and prepend operations without requiring a formal table.

Instructions

Set cell values, formulas, or number format on any range — does NOT require the worksheet to be a formal Excel table. Body: { values: [['v1','v2','v3']] } for a single row, or [['a','b'],['c','d']] for multi-row. Use this for append (target the next empty row's address, e.g. 'A172:H172'), update (target a single cell like 'H42'), or prepend-style edits (read existing, concatenate, write back). Number of inner-array values must match the column count of the address.

💡 TIP: Set cell values, formulas, or number format on any range — does NOT require the worksheet to be a formal Excel table. Body: { values: [['v1','v2','v3']] } for a single row, or [['a','b'],['c','d']] for multi-row. Use this for append (target the next empty row's address, e.g. 'A172:H172'), update (target a single cell like 'H42'), or prepend-style edits (read existing, concatenate, write back). Number of inner-array values must match the column count of the address.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
driveIdYesPath parameter: drive-id
driveItemIdYesPath parameter: driveItem-id
workbookWorksheetIdYesPath parameter: workbookWorksheet-id
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 destructiveHint=true and readOnlyHint=false, so the description adds context about setting formulas and number format. However, the body example only shows values, which might confuse agents on how to specify formulas or number format. It does not disclose any side effects beyond modification, but destructiveHint covers that. A slightly clearer specification of body keys would improve transparency.

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

Conciseness2/5

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

The description is unnecessarily long and contains a verbatim repetition of the same text (the tip duplicates the opening sentence). This wastes space and could be consolidated into a shorter, more efficient description. A single, well-structured paragraph would suffice.

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?

The description covers the body structure and use cases well, but lacks any mention of the response format (no output schema exists) or error conditions. It also does not discuss prerequisites like the address existing. For a complex tool with multiple parameters, this is moderately complete but not fully comprehensive.

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% parameter description coverage, but the body parameter is free-form with no structure. The description adds significant meaning by showing the expected structure of the body (values array) and explaining how to use it for different operations (append, update, prepend). It also explains the column count constraint, which is not in the schema.

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 it sets cell values, formulas, or number format on any range, and it does not require a formal Excel table. The verb 'update' and resource 'Excel range' are present. It distinguishes from siblings like 'clear-excel-range' and 'format-excel-range' but could more explicitly contrast with 'insert-excel-range' or 'merge-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 Guidelines4/5

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

The description provides examples of when to use this tool: for append (target next empty row), update (single cell), or prepend-style edits (read, concatenate, write back). It also explains the constraint on inner-array values matching column count. However, it does not explicitly state when not to use it or compare with alternatives like 'insert-excel-range' or 'clear-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