Skip to main content
Glama
Sign In
yahoo-access

yahoo-access

by weirdapps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

yahoo_empty_folder

Permanently delete all messages in a Yahoo Mail folder like Bulk or Trash. Defaults to a dry run returning the count that would be purged; pass confirm=True to actually empty it.

Instructions

PERMANENTLY delete ALL messages in a folder (mark \Deleted + EXPUNGE).

Intended for Bulk (spam) and Trash. Irreversible.

Safety: with confirm=False (default) NOTHING is deleted — it returns the count that WOULD be purged. Pass confirm=True to actually empty the folder.

Args: folder: Folder to empty (e.g. "Bulk", "Trash") confirm: Must be True to actually delete. Default False = dry run. account: Account key from accounts.json, e.g. "personal" or "work". Default: the account that file marks as default.

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": {
      "folder": "<folder>"
    },
    "name": "yahoo_empty_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderYes
accountNo
confirmNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the destructive mechanism, irreversibility, and the critical default-safe behavior (confirm=False returns a would-purge count and deletes nothing). This is exactly the behavioral context an agent needs before invoking 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the destructive action and safety note, then a well-organized Args block. The Args section partly restates schema field names, but since schema coverage is 0% that repetition is load-bearing rather than wasteful; a slightly leaner phrasing would be marginally better.

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?

An output schema exists, so return values needn't be spelled out, and the description still explains the meaningful return case (the dry-run count). Combined with full parameter and safety coverage for a destructive 3-param tool, nothing an agent needs is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it documents all three parameters: folder with examples, confirm with its default/dry-run semantics, and account with its source (accounts.json) and default resolution. No parameter is left ambiguous.

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 ('PERMANENTLY delete ALL messages in a folder') plus the underlying mechanism (mark \Deleted + EXPUNGE), which no sibling describes. An agent can distinguish it from yahoo_delete_mail or yahoo_move_mail from the description alone.

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 scopes intended targets ('Intended for Bulk (spam) and Trash') and flags irreversibility, giving clear when-to-use context. It does not name an alternative tool (e.g. yahoo_delete_mail) or state when NOT to use this versus a selective delete, so it falls short of a 5.

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