Skip to main content
Glama

Coline

Delete a sheet comment

delete_sheet_comment
DestructiveIdempotent

Deletes the person's own comment (a sheet's owner can delete any).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>",
      "sheetId": "<sheetId>",
      "commentId": "<commentId>"
    },
    "name": "delete_sheet_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
sheetIdYesSheet id from search, fetch or create_sheet.
commentIdYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
deletedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already disclose that this is destructive, not read-only, idempotent, and not open-world. The description adds meaningful behavioral context beyond those annotations by specifying the authorization rule: users may delete their own comments, while sheet owners may delete any comment.

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 a single compact sentence with no wasted wording, and the key scope rule is front-loaded. It communicates the deletion operation and ownership caveat efficiently.

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 destructive deletion tool with annotations and an output schema, the description covers the key permission nuance. It does not discuss side effects or error conditions, but those gaps are relatively minor given the structured metadata.

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?

The schema documents sheetId and workspace but leaves commentId without a description. The description adds some semantic meaning by indicating that the comment must be one the caller owns, unless the caller is a sheet owner, but it does not clarify parameter formats or the relationship among all three inputs.

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 states a specific verb and resource: deleting a sheet comment. It also adds a useful scope nuance by clarifying that a person can delete their own comment while a sheet owner can delete any comment, making the operation distinguishable from update/comment/list siblings.

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 ownership rule gives implied eligibility guidance, but there is no explicit guidance on when to use this tool versus updating or listing comments. It also does not state prerequisites such as required permissions beyond the owner exception.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources