Skip to main content
Glama
prmbr42-bot

Smartsheet MCP Server

by prmbr42-bot

Delete Rows from Sheet

smartsheet_delete_rows
Destructive

Permanently delete multiple rows from a Smartsheet sheet. Accepts sheet ID and row IDs; child rows are also removed. Use with caution as this operation is irreversible.

Instructions

Permanently delete one or more rows from a Smartsheet sheet. This operation is IRREVERSIBLE. Deleted rows and their cell data are permanently removed. Confirm row IDs before calling. Child rows are also deleted when parent rows are removed.

Args:

  • sheet_id (number): Target sheet ID

  • row_ids (number[]): Array of row IDs to delete (max 450 per request)

  • ignore_rows_not_found (boolean, optional): If true, silently skip non-existent row IDs

Returns: Confirmation message and updated sheet version.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheet_idYes
row_idsYes
ignore_rows_not_foundNo
Behavior5/5

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

Annotations already set destructiveHint=true, but the description adds critical details: the operation is irreversible, child rows are deleted with parents, and row IDs should be confirmed. This goes beyond the annotation's simple boolean flag to provide actionable behavioral context.

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

Conciseness5/5

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

The description is concise, with only 6 sentences. It front-loads the irreversible warning, then details parameters and return value. Every sentence adds value, no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's destructive nature and lack of output schema, the description covers all necessary context: irreversible deletion, child row behavior, parameter descriptions, confirmation guidance, and return type. It is sufficiently complete for an agent to use safely.

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 input schema has 0% description coverage, but the description explains all three parameters: sheet_id (target), row_ids (array, max 450), and ignore_rows_not_found (optional, silent skip). It adds meaning beyond the schema, though it could be more precise about data types already defined.

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's purpose: 'Permanently delete one or more rows from a Smartsheet sheet.' It specifies the verb (delete), resource (rows), and emphasizes permanence. Among siblings like smartsheet_add_rows and smartsheet_update_rows, it is well-differentiated.

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 explicitly warns about irreversibility and child row deletion, advising to confirm row IDs before use. However, it does not directly state when not to use this tool (e.g., if you need to keep row data), but the warnings imply cautious usage.

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/prmbr42-bot/smartsheet-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server