Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_folder_create

Creates a new email folder in a specified account, with an optional parent path, to help organize messages.

Instructions

Create a new email folder

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": "<name>"
    },
    "name": "email_folder_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
accountIdYes
parentPathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing. It does not say what permissions the account needs, what happens on a duplicate folder name, whether parentPath must already exist, or what the call returns on success. Only the fact that the operation creates persistent state is conveyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The single sentence is clean and front-loaded with the verb, with no filler, but for a three-parameter mutation tool it is severely under-sized rather than appropriately concise. Nothing is wasted, yet too little is said.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With three parameters at 0% schema coverage, no annotations, and no output schema to explain returns, the description should be doing substantial work and is not. An agent cannot determine required inputs' meaning or the effects of a successful call from this definition.

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

Parameters1/5

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

Schema description coverage is 0% across all three parameters, and the description mentions none of them. It never explains what accountId refers to, what name means (display name vs. path segment), or how the optional parentPath is interpreted and defaulted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb plus resource ('Create a new email folder'), which is unambiguous and readable against siblings like email_list_folders or email_delete. It does not explicitly differentiate itself from those siblings, but the create/list/delete boundary is self-evident from the names.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus alternatives, no prerequisites (e.g., an existing account or parent folder), and no exclusions. The agent must infer everything about invocation context from the name alone.

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