Skip to main content
Glama
Sign In
FireKey MCP Server

FireKey MCP Server

by partnerhbhl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

profile_delete

Deletes browser profiles by ID, sending them to trash for safe removal. Helps clean up unwanted profiles and free up storage.

Instructions

Delete browser profiles (soft delete to trash).

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": {
      "profile_id": "<profile_id>"
    },
    "name": "profile_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_idYesArray of profile IDs to delete (max 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It discloses that deletion is a soft delete to trash, indicating recoverability, but it does not mention effects on running profiles, permission requirements, or failure handling.

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?

A single concise sentence conveys the core action and the critical qualifier in parentheses without any wasted words. The information is front-loaded and easy to parse.

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

Completeness3/5

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

Adequate for a simple one-parameter delete operation; the soft-delete note addresses the main safety concern. However, with no annotations or output schema, details about side effects on active browsers and success/failure behavior are missing, though the simplicity of the tool keeps the gap modest.

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?

The schema description already fully documents profile_id as an array of profile IDs with max 100 items. The tool description adds no parameter-specific meaning, so the baseline 3 applies due to high schema coverage.

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 ('Delete browser profiles') and adds a key behavioral qualifier ('soft delete to trash'). This clearly distinguishes it from siblings like profile_delete_cache and makes the operation unambiguous.

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 given on when to use this tool versus alternatives such as profile_delete_cache. The action is self-evident, but the description does not state prerequisites, exclusions, or conditions for selecting this tool over siblings.

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