Skip to main content
Glama

clear-excel-range

Destructive

Clear cell contents, formatting, or both in an Excel range. Use to reset a worksheet section before writing fresh data.

Instructions

Invoke action clear

💡 TIP: Clear cell contents and/or formatting on the given range. Body: { applyTo: 'All' | 'Formats' | 'Contents' }. 'Contents' wipes values but keeps formatting; 'Formats' resets styling but keeps values; 'All' wipes both. Use this to reset a worksheet section before a fresh write rather than overwriting cell-by-cell.

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?

The description discloses the specific behavior of the applyTo parameter (All/Formats/Contents), explaining what happens to values and formatting in each case. This adds valuable context beyond the annotations (destructiveHint=true, readOnlyHint=false). No contradiction is present.

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 three sentences. The first sentence 'Invoke action clear' is redundant and could be removed. The tip-style second sentence and the explanatory third sentence are efficient. Overall, it is concise but not perfectly structured.

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 core action and key parameter variations. However, without an output schema, it does not mention what the tool returns (e.g., success status or nothing). It also omits prerequisites like the existence of the range. This leaves some gaps for an AI agent.

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?

With schema description coverage at 86%, the baseline is 3. The description adds meaningful semantics for the body.applyTo parameter by enumerating possible values and their effects. Other parameters (driveId, address, etc.) have adequate schema descriptions and are not expanded upon. This is sufficient but not exceptional.

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 explains that the tool clears cell contents and/or formatting from a specified range, and details the applyTo options. While the tool name 'clear-excel-range' is straightforward, the description doesn't explicitly distinguish it from siblings like 'delete-excel-range' or 'format-excel-range', though the use case is implied.

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 tip 'use this to reset a worksheet section before a fresh write rather than overwriting cell-by-cell' provides some guidance on when to use. However, there is no explicit 'when not to use' or mention of alternative tools among siblings, leaving the agent to infer appropriate contexts.

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