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.

Input Schema

TableJSON 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

TableJSON 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 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.5/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds genuinely new detail: deletion is permanent, and it enumerates exactly what a full-profile delete destroys (every reference, description and saved rule). It also discloses the return value (count of deleted references), which annotations cannot convey.

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, front-loaded with the usage trigger, then the mode branch, then the irreversibility warning and return value. No filler and every sentence carries decision-relevant information.

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?

Covers both execution paths, the destructive scope, permanence, and return semantics; with an output schema present, return values need not be elaborated further. Nothing an agent needs to call this 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 coverage is 100% and the schema descriptions already spell out the ref_ids omission semantics and the irrecoverable profile_key. The description restates this rather than adding format or constraint details beyond the schema, so the baseline 3 applies.

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?

States a specific verb (delete) and resource (profile or references), and immediately distinguishes the two operational modes via profile_key vs ref_ids. An agent can tell exactly what this tool does versus a read sibling like get_profile 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?

Explicitly scopes usage to 'when the user asks to delete their data' and clarifies the branch condition — pass ref_ids for partial deletion, omit for full profile deletion. No sibling delete tool exists to differentiate from, but no explicit 'when not to use' or prerequisites are stated.

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

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.