Taste Profile

Delete references or the profile

delete_profile

DestructiveIdempotent

Use this when the user asks to delete their data. Pass the profile_key and ref_ids to delete only those references, or leave ref_ids out to delete the whole profile: every reference, description and saved rule. Deletion is permanent. Returns how many references were deleted.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "profile_key": "tp_604a48a85c9a4da5a2a15ba7b4198f1b"
    },
    "name": "delete_profile"
  }
}

Input Schema

Name	Required	Description	Default
`ref_ids`	No	Delete only these references and keep the profile. Leave out to delete the whole profile: every reference, description and saved rule.
`profile_key`	Yes	The profile_key that add_refs returned. Keep it: it is the only way back to this profile and it is not recoverable.

Output Schema

Name	Required	Description
`as_of`	Yes	UTC date of this answer.
`source`	Yes
`status`	Yes
`deleted`	Yes
`refs_deleted`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

addedInput schema / examples

Added value: +[
+  {
+    "profile_key": "tp_604a48a85c9a4da5a2a15ba7b4198f1b"
+  }
+]

Changed1 schema field changedOct 5, 2026

removedOutput schema / properties / note_from_openkrill

Removed value: -{
-  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
-  "type": "string"
-}

Changed1 schema field changedOct 4, 2026

addedOutput schema / properties / note_from_openkrill

Added value: +{
+  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description still adds meaningful context beyond annotations: deletion is permanent, and omitting ref_ids destroys every reference, description, and saved rule. It does not discuss auth requirements or idempotency, but the destruction scope is well disclosed.

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?

The description is four short sentences, front-loads the usage trigger, then explains the two modes, permanence, and return behavior without wasted words.

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

Completeness5/5

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

For a destructive two-parameter tool with full schema coverage, annotations, and an output schema, the description covers when to use it, what gets destroyed, the partial-vs-full deletion distinction, and permanence. Nothing essential 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%, so both parameters are already documented in the schema, including the conditional meaning of ref_ids. The description restates that conditional behavior rather than adding new syntax or format details, making the baseline 3 appropriate.

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 states a specific verb and resource—deleting a profile or selected references—and clearly distinguishes the two operating modes. An agent can tell exactly what the tool does without opening the schema.

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?

It gives an explicit trigger: 'Use this when the user asks to delete their data,' and explains the conditional mode when ref_ids is supplied or omitted. It does not name when-not-to-use cases or alternative tools, but the usage context is clear.

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

All Taste Profile tools Inspect

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.