Skip to main content
Glama
Sign In
floppydata-mcp

floppydata-mcp

Official
by Floppydata
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_browser_session

Remove an ended Cloud Browser session from history by session ID. Browser settings persist; use delete_browser_settings to manage saved settings.

Instructions

Delete an ended Cloud Browser session from history. Persistent browser settings are kept; use delete_browser_settings for those.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "delete_browser_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYesBrowser session id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses the blast radius ('Persistent browser settings are kept'), which distinguishes it from a destructive settings wipe, but omits irreversibility, permission requirements, and the failure behavior for non-ended sessions.

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?

Two short sentences, front-loaded with the action and scope, with the sibling pointer placed last. No filler or redundancy.

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 single-param delete with no output schema, the description covers purpose, the preserved-settings side effect, and the alternative tool. The remaining gap is mutation semantics (permanence/irreversibility), which matters more here because there are no annotations to signal it.

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 single sessionId param is fully documented in the schema with format and pattern constraints. The description adds no syntax or format meaning beyond it, 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 and resource ('Delete an ended Cloud Browser session from history') and scopes it precisely to ended sessions. It also names the sibling it is not (delete_browser_settings), so an agent can discriminate without opening either 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 routes the settings case to delete_browser_settings and constrains scope to 'ended' sessions. It does not state what to do with a still-running session (e.g., stop_browser_session first) or that deletion is only valid post-termination, so guidance is clear but not exhaustive.

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