Skip to main content
Glama

search_emails

Search Outlook emails by query and return matching messages, with an optional limit on the number of results.

Instructions

Search for emails using a search query

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": {
      "query": "<query>"
    },
    "name": "search_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoMaximum number of results to return (default: 10)
queryYesSearch query to find emails

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/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 burden of behavioral disclosure; it says nothing about what fields are searched (subject, body, sender), case sensitivity, permissions, result ordering, or pagination. Only a read-like intent is weakly implied by 'search'.

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 sentence, front-loaded with the action. There is no filler, though the extreme brevity reflects missing content rather than disciplined editing.

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

Completeness2/5

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

For a search tool with no annotations and no output schema, the description is incomplete: it omits searchable fields, result behavior, and how it relates to list_emails. The structured schema covers parameters, but behavior needed to call the tool confidently is absent.

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 coverage is 100% and both parameters are documented there, so the description is not required to explain them. It adds no meaning beyond the schema; 'search query' simply echoes the query parameter and does not clarify the top parameter.

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

Purpose3/5

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

The description names the verb 'search' and resource 'emails', so the general action is clear, but 'using a search query' merely restates the required parameter and adds no scope or distinction from sibling tools like list_emails. This is minimally viable rather than informative.

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 list_emails, get_email, or other siblings, nor any prerequisites or exclusions. The agent must infer the use case entirely from the name.

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