Skip to main content
Glama
avivsinai

langfuse-mcp

by avivsinai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

delete_dataset_run

Delete a dataset run, or explicitly remove its traces to also delete observations and scores. Set delete_traces=True when the legacy delete route is unavailable.

Instructions

Delete a run through the legacy route, or explicitly delete its traces after removal.

Trace deletion also removes observations and related scores. Set delete_traces=True to allow this broader replacement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
run_nameYesThe dataset run name to delete
dataset_nameYesThe name of the dataset that owns the run
delete_tracesNoAllow trace deletion when the legacy run-delete route is unavailable

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.1
    • addedInput schema / properties / delete_traces
      Added value: +{
+  "default": false,
+  "description": "Allow trace deletion when the legacy run-delete route is unavailable",
+  "title": "Delete Traces",
+  "type": "boolean"
+}
  2. Addedv1.25.1

TDQS

A3.8/5.0
Behavior3/5

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

Because no annotations are provided, the description carries the behavioral disclosure burden. It usefully reveals that trace deletion cascades to observations and related scores, which is important side-effect information. However, it does not state irreversibility, what happens when delete_traces is false and the legacy route is unavailable, or any failure/return semantics.

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?

The definition is compact: three sentences cover the main operation, the important side effect, and the flag decision. The first sentence front-loads the purpose, though the 'or... after removal' wording is slightly convoluted.

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?

With an existing output schema and well-described parameters, the remaining needs are the conditional behavior and cascading side effects, both of which are at least partially covered. The main gap is not explicitly describing the failure mode when delete_traces is left false and the legacy route is unavailable.

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?

All three parameters are already fully documented in the schema, so the baseline is 3. The description adds genuine value beyond the schema by explaining that delete_traces=True triggers a broader trace-deletion path that also removes observations and related scores.

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 clearly identifies the target resource: deleting a dataset run, and it is distinct from sibling dataset-item or annotation-queue tools. However, the phrase 'through the legacy route, or explicitly delete its traces after removal' is somewhat ambiguous about whether these are two modes or a sequence.

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 gives concrete conditional guidance: set delete_traces=True to enable the broader trace-deletion replacement, and the schema adds that this applies when the legacy route is unavailable. It does not name sibling alternatives or explicitly state when not to use the tool, but the context is clear enough for correct invocation.

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

Deploy Server

Other Tools