Skip to main content
Glama
prmbr42-bot

Smartsheet MCP Server

by prmbr42-bot

Delete Attachment

smartsheet_delete_attachment
Destructive

Delete an attachment permanently from a Smartsheet sheet. Provide the sheet ID and attachment ID to remove the file irreversibly.

Instructions

Permanently delete an attachment from a Smartsheet sheet. This action is IRREVERSIBLE. Verify the attachment ID before proceeding.

Args:

  • sheet_id (number): Sheet ID containing the attachment

  • attachment_id (number): Attachment ID to delete

Returns: Deletion confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheet_idYes
attachment_idYes
Behavior4/5

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

Annotations already set destructiveHint=true. The description reinforces this by stating 'IRREVERSIBLE' in all caps, adding emphasis beyond the annotation. No other behavioral traits (e.g., permissions, rate limits) are mentioned, but the confirmation aligns with annotations.

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?

Description is concise with three sentences plus Args/Returns sections. The irreversible warning is front-loaded. Returns section is minimal but adequate.

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?

For a simple delete operation, the description covers purpose, parameters, and outcome (deletion confirmation). No output schema, but the description provides sufficient context for an agent to invoke the tool 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?

Input schema has 0% description coverage, but the description lists both parameters with clear explanations: 'Sheet ID containing the attachment' and 'Attachment ID to delete.' This adds meaning beyond the schema's raw constraints, compensating for the lack of schema descriptions.

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 'Permanently delete an attachment from a Smartsheet sheet,' specifying the verb (delete) and resource (attachment). This distinguishes it from sibling tools like smartsheet_delete_comment or smartsheet_delete_rows.

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?

Explicitly warns to verify the attachment ID before proceeding due to irreversibility. While it doesn't name alternative tools for non-destructive actions, the caution provides clear usage guidance.

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