Skip to main content
Glama

manage-contact

Manage personal contacts in Outlook: list, search, get, create, update, or delete contacts with detailed fields.

Instructions

Manage personal contacts. action=list (default) lists contacts. action=search searches by name/email. action=get retrieves full details. action=create adds a contact. action=update modifies a contact. action=delete removes a contact.

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

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

Annotations indicate readOnlyHint=false and destructiveHint=false, which aligns with the description's inclusion of create and delete actions. However, description does not disclose side effects, permission needs, or behavioral nuances for each action beyond their basic definition.

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 a concise list of actions and associated parameters, front-loaded with the general purpose. It is efficient but could be more structured with bullet points or sections.

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, so the description must cover input and behavior. It covers all 16 parameters and all 6 actions, including pagination and output verbosity. Complete for a multi-action tool.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by mapping parameters to specific actions (e.g., query for search, id for get/update/delete) and explaining defaults. This goes beyond the schema alone.

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 clearly states it manages personal contacts and enumerates all supported actions (list, search, get, create, update, delete). However, it does not differentiate from sibling tools like search-people, which also searches people. The purpose is clear but not uniquely distinguished.

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

Usage Guidelines3/5

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

The description lists actions and their defaults, but does not explicitly state when to use this tool vs alternatives like search-people or folders. No guidance on when not to use or prerequisites.

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