Savri Analytics MCP Server

Delete Event Property

savri_delete_property

Remove an event property and all its stored values from Savri Analytics to clean up data and maintain organized tracking.

Instructions

Delete an event property. This will also remove all stored values for this property.

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": {
      "site_id": "<site_id>",
      "name": "<name>"
    },
    "name": "savri_delete_property"
  }
}

Input Schema

Name	Required	Description	Default
`site_id`	Yes	Site ID
`name`	Yes	Property name to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jan 26, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden. It discloses the destructive consequence ('remove all stored values'), which is valuable, but doesn't mention permissions needed, irreversibility, side effects on related data, or error conditions. For a deletion tool with zero annotation coverage, this leaves significant behavioral gaps.

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?

Two sentences, zero waste. The first states the action, the second clarifies the consequence. It's front-loaded with the primary purpose and appropriately sized without redundant information.

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?

Given this is a destructive deletion tool with no annotations and no output schema, the description is incomplete. It should address permissions, confirmation needs, or what happens to associated data beyond values. The sibling tools include list_properties, but no guidance on verification before deletion is provided.

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 the schema already documents both parameters (site_id and name). The description doesn't add meaning beyond what the schema provides, such as format examples or constraints. Baseline 3 is appropriate when schema does the heavy lifting.

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 the specific action ('Delete an event property') and distinguishes it from siblings by specifying it removes property values, unlike list or get tools. It uses precise verb+resource terminology that differentiates from creation/deletion of other entities like funnels or goals.

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?

No guidance is provided on when to use this tool versus alternatives. While siblings include list_properties and create_property, the description doesn't mention prerequisites, confirmations, or when deletion is appropriate versus modification. It lacks explicit when/when-not instructions or named alternatives.

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

Deploy Server