Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_remove_account

Remove a stored email account by deleting credentials, revoking Gmail access, and clearing Outlook tokens from the local cache, with a report on provider-side revocation success.

Instructions

Remove an email account: deletes its stored credentials, revokes the Google grant for Gmail accounts, and removes Outlook tokens from the local token cache. The result reports whether provider-side revocation succeeded.

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": {
      "accountId": "<accountId>"
    },
    "name": "email_remove_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdYesID of the account to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses exactly what is destroyed (credentials, Google grant, cached Outlook tokens) and what the result reports (provider-side revocation success). It does not state whether the operation is irreversible or what happens if revocation fails, which keeps it short of a 5.

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 sentences, front-loaded with the operation and its effects, then the return-value note. No filler or repetition of the tool name beyond what is needed to establish scope.

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 one-parameter destructive tool with no annotations and no output schema, the description covers the mutation's scope and the shape of the response. Only the irreversibility/permission context and the fate of local mail data are left unstated.

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?

There is a single required parameter, accountId, with 100% schema description coverage ('ID of the account to remove'), so the schema already does the work. The description adds no further detail such as accepted ID formats or how to obtain the ID, so it sits at the baseline.

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 (remove) and resource (email account), then enumerates the concrete effects: deleting stored credentials, revoking the Google grant, and clearing Outlook tokens from the local cache. This clearly separates it from siblings like email_add_account or email_delete, which operate on messages rather than the account itself.

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

Usage Guidelines3/5

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

Usage is implied by the operation itself, but there is no explicit when-to-use guidance, no prerequisites (e.g., whether mail data must be deleted first), and no named alternatives such as email_add_account for re-adding. An agent can infer the context but must reason about it.

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