Skip to main content
Glama

manage-contact

Destructive

Manage personal Outlook contacts with actions to list, search, get, create, update, and delete contacts. Supports pagination and output verbosity control.

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)
Behavior5/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false. The description expands on this by detailing that delete is permanent, update patches only given fields, and outlines each action's behavior. No contradictions.

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?

The description is well-structured: first sentence gives overall purpose, then each action is described in separate bullets, followed by outputVerbosity and sibling comparison. Every sentence adds necessary information without redundancy.

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

Completeness5/5

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

With 16 parameters, no output schema, and multiple actions, the description covers all actions, their required parameters, defaults, and pagination. It lacks return details but is still comprehensive given the lack of output schema.

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 value: it explains defaults, which action each param is for, and that `skip` should use value from previous page. It also describes mapping for firstName/lastName to Graph fields, surpassing the schema alone.

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 starts by stating 'Full CRUD over the signed-in user's personal Outlook contacts (destructive: covers `delete` action).' It then enumerates each action (list, search, get, create, update, delete) with specific behaviors, clearly distinguishing from sibling tool 'search-people'.

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 context: it mentions destructive nature, default values for count/skip, and suggests 'Prefer `search-people` for cross-source relevance ranking — this tool only searches your personal contact store.' This clearly guides when to use an alternative.

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-mcp'

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