Skip to main content
Glama

delete-excel-table-row

Destructive

Remove a specific row from an Excel table by its zero-based index.

Instructions

Delete a single row from a formal Excel table by zero-based row index.

💡 TIP: Delete a single row from a formal Excel table by zero-based row index.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
driveIdYesPath parameter: drive-id
driveItemIdYesPath parameter: driveItem-id
workbookTableIdYesPath parameter: workbookTable-id
indexYesPath parameter: index
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?

The description states 'delete' which aligns with annotations (destructiveHint=true). It does not disclose additional behavioral traits such as row reindexing after deletion. The annotations already cover destructive nature, so no contradiction.

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 only two sentences, but the second sentence is a repetition of the first ('💡 TIP: ...'). This redundancy wastes space without adding value. Could be more concise.

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 basic operation but lacks details on return values (no output schema) and side effects like row shifting. For a delete tool, additional context on irreversibility would improve completeness.

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?

Input schema has 100% coverage and clear parameter descriptions. The tool description adds no new information beyond the schema. The phrase 'zero-based row index' mirrors the schema description for the 'index' parameter.

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 that the tool deletes a single row from a formal Excel table by zero-based index. However, it does not differentiate from sibling tools like delete-excel-range or update-excel-table-row, which could lead to confusion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No usage guidelines are provided. The description does not specify when to use this tool versus alternatives, nor does it mention prerequisites or restrictions (e.g., cannot delete header row).

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