Skip to main content
Glama
Upload-Post

Upload-Post

Official
by Upload-Post
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete profile

delete_user
Destructive

Permanently deletes a profile and disconnects its linked social accounts only when the user confirms by retyping the profile name; otherwise it previews what would be removed.

Instructions

Permanently delete a profile and disconnect its socials. Needs the user's approval: the call only deletes when confirm_username repeats the profile name, typed or approved by the user. Without it the response says what would be deleted.

Input Schema

NameRequiredDescriptionDefault
usernameYes
confirm_usernameNoThe profile name typed again by the user to confirm the deletion. Must equal `username`; otherwise nothing is deleted.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.17.2
    • addedInput schema / properties / confirm_username
      Added value: +{
+  "description": "The profile name typed again by the user to confirm the deletion. Must equal `username`; otherwise nothing is deleted.",
+  "type": "string"
+}
  2. Changed2 schema fields changedv0.11.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. First observedv0.4.0

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description explains that deletion is permanent, disconnects socials, requires user approval via confirm_username, and returns a preview of what would be deleted when confirmation is absent. This adds substantial behavioral context for a destructive operation.

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 compact and front-loaded, starting with the permanent deletion effect and then the confirmation requirement. Every sentence adds safety-relevant information without repetition.

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 tool with annotations and an output schema, the description covers the key missing context: permanence, social disconnection, confirmation behavior, and the no-confirm preview response. No critical invocation detail appears absent.

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?

The schema documents confirm_username, and the description reinforces its safety role: it must repeat the profile name and otherwise nothing is deleted. The username parameter is only indirectly described as the profile name, which is adequate but not fully detailed.

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 states a specific verb and resource: permanently delete a profile and disconnect its socials. This clearly separates it from siblings like create_user and list_users by operation type, though it does not explicitly name alternatives.

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?

It gives an important usage condition: deletion only occurs when confirm_username repeats the profile name and the user approves. However, it does not explicitly compare this tool with alternatives such as list_users or create_user, so guidance is implied rather than complete.

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