Skip to main content
Glama

Mail Get Links

mail_get_links

Extracts hyperlinks from a single email using its message ID, helping you collect and review all links without manual searching.

Instructions

Extract hyperlinks from one email.

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": {
      "message_id": "<message_id>"
    },
    "name": "mail_get_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not say whether the operation is read-only, how links are returned (raw list vs deduplicated, HTML vs plain-text sources), or what happens with an invalid message_id. For a read tool this is a significant disclosure gap.

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?

One short, front-loaded sentence with zero wasted wording. Its brevity is efficient, though it verges on under-specification rather than verbosity.

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

Completeness3/5

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

The tool is simple (one parameter, no output schema), so a short description is defensible, but an agent still lacks the message_id format and any hint about the shape of the extracted-link result. Given zero annotation coverage, the description does not fully cover what an agent needs to invoke it correctly.

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

Parameters2/5

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

Schema description coverage is 0% and the single required parameter message_id is never explained in the description — its expected format and provenance (e.g., from mail_search or mail_get_emails) are left entirely to inference. The description adds no meaning beyond the bare schema property name.

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?

The description names a specific verb ("Extract") and resource ("hyperlinks") with a clear scope ("from one email"), which distinguishes it from siblings like mail_get_email or mail_search. It stops short of explicitly differentiating from those siblings, but the operation is unambiguous.

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 instead of mail_get_email (which may also surface links) or mail_search. No prerequisites are stated, such as whether the email must be fetched first or whether the message_id must come from a prior search.

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