Skip to main content
Glama
Sign In

twelvebit Analytics

by app.twelvebit
OverviewDiscussionsAdmin

Delete a saved segment

delete_segment
DestructiveIdempotent

Delete a saved segment by id or name. Needs confirm: true; without it the tool only shows what it would delete. Visit data stays.

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": {
      "segment": "<segment>"
    },
    "name": "delete_segment"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoSite domain (example.com), id or public id (tb_…). Optional with a site key, or when the account has one site.
confirmNoSet to true to really do it. Without it, the tool only describes what it would do.
segmentYesSegment id or name (from list_segments).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds two pieces of behavior not in the structured fields: the dry-run default without confirm, and the data-retention note that 'Visit data stays', which prevents an agent from assuming visit records are destroyed with the segment.

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?

Three short sentences, no filler, and the destructive action plus its confirm gate are front-loaded where an agent will read them first. Every clause carries information.

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 3-parameter delete with no output schema, the description covers the identifier, the confirmation gate, the preview behavior, and data retention. It could say what the preview returns or what happens to alerts/funnels referencing the segment, but nothing essential to calling it correctly is missing.

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%, and the description's parameter content ('by id or name', 'Needs confirm: true') essentially restates the schema rather than extending it. Baseline 3 applies since the schema carries the detail work.

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?

States a specific verb and resource ('Delete a saved segment') plus the accepted identifier forms (id or name), which is unambiguous. It does not explicitly name siblings like list_segments or save_segment, but the delete-vs-save distinction is self-evident from the verb.

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 description tells the agent how to activate a real deletion (confirm: true) versus a preview, which is practical guidance. It stops short of saying when deletion is the right choice over alternatives (e.g. updating or leaving a segment in place) or what preconditions exist beyond the confirm flag.

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

All twelvebit Analytics toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources