Skip to main content
Glama

manage-contact

Destructive

Add, update, delete, or search personal Outlook contacts. List contacts with pagination, or get full details by ID.

Instructions

Full CRUD over the signed-in user's personal Outlook contacts (destructive: covers delete action). action=list (default) returns contacts with pagination via skip/count (default 50). action=search returns contacts matching query against name/email (default 25). action=get returns full contact detail by id. action=create adds a new contact and returns its id. action=update patches the given fields by id (only fields passed are changed). action=delete permanently removes the contact by id. Use outputVerbosity (minimal/standard/full) on list/search to control field count. Prefer search-people for cross-source relevance ranking (contacts + directory + recent comms) — this tool only searches your personal contact store.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoAction to perform (default: list)
countNoNumber of results (action=list default: 50, action=search default: 25)
skipNoPagination offset for action=list (default: 0). Use the value suggested by the previous page response.
folderNoContact folder ID (action=list)
outputVerbosityNoOutput detail level (action=list/search, default: standard)
queryNoSearch query for name or email (action=search, required)
idNoContact ID (action=get/update/delete, required)
displayNameNoFull name (action=create/update)
firstNameNoGiven name (action=create/update). Maps to Graph `givenName`. If displayName not provided, will be combined with lastName.
lastNameNoSurname (action=create/update). Maps to Graph `surname`.
emailNoPrimary email address (action=create/update)
emailsNoMultiple email addresses (action=create/update). First entry is primary.
mobilePhoneNoMobile phone number (action=create/update)
companyNameNoCompany name (action=create/update)
jobTitleNoJob title (action=create/update)
notesNoPersonal notes (action=create/update)
Behavior4/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds context that 'delete permanently removes the contact' and that 'update' is a patch (only passed fields changed). No contradictions, and it adds value beyond annotations.

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?

The description is well-structured, starting with a high-level overview, then detailing each action, and ending with an alternative. It is appropriately sized for a multi-action tool with 16 parameters, though a slightly more condensed phrasing could improve conciseness.

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 complex tool with 6 actions and no output schema, the description covers return behaviors (e.g., list returns paginated contacts, create returns id) and default behaviors. It lacks details on full response structure but provides sufficient context for proper invocation.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant meaning: default counts per action, pagination skip using previous page's suggestion, outputVerbosity defaults, firstName mapping to Graph givenName, and emails first entry being primary. This richly supplements the schema.

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?

The description explicitly states it provides 'Full CRUD over the signed-in user's personal Outlook contacts' and enumerates each action (list, search, get, create, update, delete) with clear purposes. It also distinguishes from the sibling tool 'search-people' by noting this tool only searches personal contacts, making it easy for an agent to select correctly.

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?

The description provides explicit guidance on when to use this tool vs. the alternative 'search-people' (cross-source relevance ranking). It details default values for count per action, pagination via skip, and that outputVerbosity controls field count, giving clear context for usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/littlebearapps/outlook-assistant'

If you have feedback or need assistance with the MCP directory API, please join our Discord server