Skip to main content
Glama

clear-excel-range

Destructive

Clear cell content and formatting on a specified Excel range. Choose between clearing all, only formats, or only contents to reset a section before new 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
Behavior5/5

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

The description discloses the three modes (All, Formats, Contents) and their effects, such as 'wipes values but keeps formatting' and 'resets styling but keeps values', which aligns with the destructiveHint annotation. It adds valuable behavioral context beyond the annotation.

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 composed of two concise sentences and a tip. The first sentence is somewhat redundant ('Invoke action clear'), but the rest is efficient and front-loaded with the action and use case.

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 the tool's complexity (clearing with options) and no output schema, the description covers the essential behavior and usage. It lacks prerequisites (e.g., range existence) but overall provides sufficient context for an agent to select and invoke correctly.

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 description explains the body parameter's applyTo field with three specific options and their behavior, which adds meaning beyond the schema's type-only definition. The other parameters are path identifiers with schema descriptions already provided, so the description compensates for the key parameter.

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 clears cell contents and/or formatting on an Excel range, distinguishing it from delete-excel-range which removes the range entirely. It specifies the resource and action with precision.

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 advises using this tool 'to reset a worksheet section before a fresh write rather than overwriting cell-by-cell', providing clear context. It doesn't explicitly state when not to use, but the distinction from deleting 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