Local MCP

Web Session Delete

web_session_delete

Destructive

Deletes a SAVED web-automation login profile: closes its window if open, erases its cookies and site data from this Mac, and removes it from web_session_list. Use it to clean up a profile that is no longer needed — web_session_close only closes the window and leaves the login (and its cookies) on disk. IRREVERSIBLE: the next web_login for that name starts from a signed-out browser. Requires confirm=true; without it you get a preview. Verify with web_session_list, which must no longer list the name.

Input Schema

Name	Required	Description
`confirm`	No	Must be true to actually delete. Without it, returns a preview and deletes nothing.
`session`	No	Name of the profile to delete, as web_session_list reports it. Defaults to 'default'.
`remember`	No	With confirm: true, also stop asking for this kind of action from now on. Only when the person said so ("don't ask again"). The person can revoke it in LMCP or with set_always_allowed.

Output Schema

Name	Required	Description
`ok`	No	True only when BOTH halves are done: data erased and name removed from the list
`note`	No	Present when store_removed is false: what was erased and what was kept
`closed`	No	Whether a live window had to be closed first
`deleted`	No	The profile name that was deleted
`data_removed`	No	Whether the cookies and site data were erased
`store_removed`	No	False when the data was erased but WebKit kept the profile's empty container (still open in Local MCP's browser process); nothing is left to retry
`name_forgotten`	No	Whether the name was removed from web_session_list

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026

addedInput schema / properties / remember

Added value: +{
+  "description": "With confirm: true, also stop asking for this kind of action from now on. Only when the person said so (\"don't ask again\"). The person can revoke it in LMCP or with set_always_allowed.",
+  "type": "boolean"
+}

Changed2 schema fields changedOct 22, 2026

addedOutput schema / properties / note

Added value: +{
+  "description": "Present when store_removed is false: what was erased and what was kept",
+  "type": "string"
+}

addedOutput schema / properties / store_removed

Added value: +{
+  "description": "False when the data was erased but WebKit kept the profile's empty container (still open in Local MCP's browser process); nothing is left to retry",
+  "type": "boolean"
+}

AddedAug 26, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds substantial context beyond that: it closes the window if open, erases cookies and site data from the Mac, removes the profile from web_session_list, and is irreversible because the next web_login starts signed out. It also states the confirm=true requirement and preview behavior.

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 front-loaded with the core action and scope, then proceeds through caveats, alternatives, irreversibility, confirmation, and verification. Every sentence contributes to correct invocation without unnecessary 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?

The tool has an output schema, full annotations, and complete schema descriptions, and the description adds enough behavioral context to fully cover the risks and workflow. It is complete for a destructive cleanup operation.

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 all three parameters are fully documented in the schema. The description reinforces the confirm preview behavior and session naming, but it does not add syntax or meaning beyond what the schema already provides, and it does not mention the 'remember' option covered by the schema. Baseline 3 is 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 uses a specific verb and resource: 'Deletes a SAVED web-automation login profile,' and immediately clarifies the scope by contrasting it with web_session_close. It leaves no ambiguity about what is being deleted versus merely closed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use this tool ('clean up a profile that is no longer needed') and when not to use it ('web_session_close only closes the window and leaves the login on disk'). It also directs the agent to verify via web_session_list afterward.

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

All Local MCP 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.