Skip to main content
Glama
Grist MCP Server
by nic01asFr

Delete Grist Records

delete_grist_records

Deletes specified records from a Grist table using document, table, and record IDs. Use it to remove unwanted rows or clean up data programmatically.

Instructions

Supprime des enregistrements d'une table Grist.

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": {
      "doc_id": "<doc_id>",
      "table_id": "<table_id>",
      "record_ids": "<record_ids>"
    },
    "name": "delete_grist_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYesL'ID du document
table_idYesL'ID de la table
record_idsYesListe des IDs des enregistrements à supprimer

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.2
    • addedInput schema / properties / doc_id / description
      Added value: +"L'ID du document"
    • addedInput schema / properties / record_ids / description
      Added value: +"Liste des IDs des enregistrements à supprimer"
    • addedInput schema / properties / table_id / description
      Added value: +"L'ID de la table"
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing beyond the bare fact of deletion. It does not say whether deletion is permanent or reversible, whether all record_ids are removed atomically on failure, or what permissions are required — critical gaps for a destructive batch mutation.

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?

A single efficient sentence with no filler or redundancy. It is appropriately sized but arguably under-specified rather than over-written.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, and parameters are fully covered by the schema. But for an unannotated destructive mutation, the description omits irreversibility, batch failure semantics, and permission requirements, leaving the agent without the context needed to invoke it safely.

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?

Schema description coverage is 100%, so doc_id, table_id, and record_ids are already documented in the schema. The description adds no additional meaning such as ID format, maximum batch size, or behavior for non-existent record IDs, so the baseline of 3 applies.

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 ('Supprime des enregistrements d'une table Grist'), so an agent immediately knows this removes row records from a table. However, it offers no differentiation from sibling deletion tools such as delete_column, delete_document, or delete_document_history.

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?

There is no guidance on when to use this versus update_grist_records or the other delete_* siblings, and no mention of preconditions. The agent must infer the use case entirely from the name.

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