Skip to main content
Glama

local-mcp

by com.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

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust be true to actually delete. Without it, returns a preview and deletes nothing.
sessionNoName of the profile to delete, as web_session_list reports it. Defaults to 'default'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNoTrue only when BOTH halves are done: data erased and name removed from the list
closedNoWhether a live window had to be closed first
deletedNoThe profile name that was deleted
data_removedNoWhether the cookies and site data were erased
name_forgottenNoWhether the name was removed from web_session_list

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already carry destructiveHint=true, but the description adds substantial behavioral context: what gets destroyed (window, cookies, site data, list entry), the IRREVERSIBLE consequence (next web_login starts signed-out), and the confirm-gate behavior (without confirm=true it only previews). This is exactly the kind of beyond-annotations transparency that matters for a destructive tool.

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?

Four sentences, each earning its place: what it deletes, when to use it versus the sibling, the irreversibility warning, and the confirm/verify steps. The most safety-critical information (IRREVERSIBLE) is front-loaded and emphasized, with no filler or repetition of schema content.

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 2-parameter tool with an output schema present, this description is fully sufficient: it covers the action scope, the alternative tool, the irreversible consequence, the confirmation guardrail, and a verification step. There is no operational gap an agent would need to guess about.

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 both confirm and session are already fully documented in the schema. The description reinforces the confirm=true requirement and mentions the preview behavior, but adds no genuinely new parameter meaning beyond what the schema provides. 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?

States a precise verb ('Deletes') and resource ('SAVED web-automation login profile'), then enumerates the exact scope of deletion: closes the window, erases cookies/site data, removes from web_session_list. It also names the sibling it is not (web_session_close), so an agent can distinguish it from the close-only alternative 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 Guidelines5/5

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

Explicitly says when to use it ('clean up a profile that is no longer needed') and when to use the alternative instead ('web_session_close only closes the window and leaves the login on disk'). Adds a post-condition check ('Verify with web_session_list'), giving the agent a complete decision and verification workflow.

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

All local-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation3/5

Many tools are clearly distinct per app (e.g., chrome_*, safari_*, m365_*), but there is notable overlap between generic file tools like `file_list` and `finder_list`, both listing files; `search_contacts` and `list_contacts` serve similar purposes; `report_friction` and `report_problem` both send feedback to the team. The large number of tools with similar purposes in different domains creates moderate ambiguity for an agent.

Naming Consistency4/5

The naming convention is very consistent overall: most tools follow a `{app}_action` or `verb_noun` pattern (e.g., `chrome_click`, `create_calendar_event`, `list_reminders`). There are minor deviations like `lmcp_install_upgrade` (two verbs) and `complete_omnifocus_task` vs. `complete_reminder` (inconsistent verb placement). Still, the pattern is predictable and readable across the full set.

Tool Count2/5

With 225 tools, the surface is extremely large and heavy. While it covers many distinct domains (browsers, mail, calendar, files, notes, reminders, video editing, web automation, etc.), the sheer number makes it hard to navigate and likely includes many rarely-used tools. This is far beyond the well-scoped range of 3-15 tools and feels excessive even for a 'local everything' MCP server.

Completeness3/5

For many app integrations, the tool set provides solid CRUD coverage (e.g., Calendar has create, read, update, delete; Apple Notes has create, read, update, list, search; OmniFocus has create, list, search, complete). However, some areas are incomplete: for example, there is no tool to create a new Mail folder or delete notes. The 'web' tools lack a clear update/delete for saved sessions. The suite is broad but has notable gaps within individual domains.

Resources