tracecat_delete_row
Delete a specific row from a Tracecat table by providing the table ID and row ID.
Instructions
Delete a row from a table
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| table_id | Yes | Table ID | |
| row_id | Yes | Row ID |
Delete a specific row from a Tracecat table by providing the table ID and row ID.
Delete a row from a table
| Name | Required | Description | Default |
|---|---|---|---|
| table_id | Yes | Table ID | |
| row_id | Yes | Row ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description only states the operation with no disclosure of consequences, permissions, or irreversibility; minimal 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, no unnecessary words; efficient but somewhat underspecified; earns its place without waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema and no annotations; description lacks details about return values, error handling, or post-deletion state; incomplete for a mutation tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% with basic descriptions for both parameters; tool description adds no additional meaning beyond what schema already provides; baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states verb 'Delete' and resource 'a row from a table', but does not distinguish from sibling delete tools like tracecat_delete_action; however, the name itself provides specificity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like tracecat_batch_insert_rows or tracecat_update_row; no prerequisites or exclusions mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/adrojis/tracecat-mcp-community'
If you have feedback or need assistance with the MCP directory API, please join our Discord server