Skip to main content
Glama

Export Contacts to Local File

export_contacts

Export all Microsoft 365 contacts, including every contact folder and field, to a local JSON file for reconciliation or bulk processing.

Instructions

Export every contact in the signed-in mailbox to a local JSON file and return its path. Covers the default Contacts folder and every contact folder beneath it, with all fields (emails, phones, addresses, categories, birthday, notes, folder path). Use this to reconcile or bulk-process contacts; use list_contacts or search_contacts to look one up.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
out_dirNoDirectory to write into (default: the system temp directory)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds meaningful context beyond them: the export is recursive across all contact folders, includes a named field set, and returns the written path. It stops short of disclosing the filename chosen, whether an existing file is overwritten, or any location/permission constraints beyond the out_dir param.

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 scope and return value, then the use/when-not pair. No filler or redundant restatement of the title.

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?

No output schema exists, but the description compensates by stating the return value is the file path. Scope (all folders, all fields) is complete for a single-optional-param tool; only the on-disk file naming and overwrite behavior 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?

Schema description coverage is 100% and out_dir is fully documented in the schema, so baseline 3 applies. The description does not mention out_dir at all, adding nothing beyond the structured field, though nothing is left ambiguous either.

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 ("Export every contact in the signed-in mailbox to a local JSON file") plus the return value ("return its path"). It also names the sibling tools it is not (list_contacts, search_contacts), so an agent can distinguish it without opening any schema.

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

Usage Guidelines5/5

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

Explicitly gives the use case ("reconcile or bulk-process contacts") and the exclusion with the alternative ("use list_contacts or search_contacts to look one up"). The routing decision is fully determined.

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