Skip to main content
Glama

m365_contacts_update

DestructiveIdempotent

Update or clear Microsoft 365 contact fields like name, email, phone, and address. Provide the contact ID and only the fields to modify or clear.

Instructions

Update or clear contact fields; use empty strings or arrays to clear supported values

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoSingle-email convenience field
notesNoPersonal-notes convenience field
titleNoCourtesy title, such as Dr. or Ms.
fileAsNo
companyNoCompany-name convenience field
managerNo
surnameNoLast name
birthdayNoISO 8601 date-time in UTC
childrenNoChildren names; empty clears the list
folderIdNoOptional contact folder ID; omit for the default Contacts folder
jobTitleNo
nickNameNo
contactIdYes
givenNameNoFirst name
categoriesNoOutlook category names; empty removes all categories
departmentNo
generationNoName suffix, such as Jr.
homePhonesNoComplete home phone list; empty clears it
middleNameNo
professionNo
spouseNameNo
companyNameNo
displayNameNo
homeAddressNo
imAddressesNoInstant-messaging addresses; empty clears the list
mobilePhoneNo
otherAddressNo
assistantNameNo
businessPhoneNoSingle-business-phone convenience field
personalNotesNo
businessPhonesNoComplete business phone list; empty clears it
emailAddressesNoComplete email list; an empty array clears all email addresses
officeLocationNo
parentFolderIdNoParent folder ID when folderId identifies a direct child folder
businessAddressNo
businessHomePageNo
Behavior4/5

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

The description adds a key behavioral trait—using empty strings or arrays to clear values—which goes beyond the annotations. Annotations already cover destructive and idempotent hints, so this extra context is valuable and not contradictory.

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?

A single, front-loaded sentence that states the action and the key clearing behavior without waste. Every word earns its place.

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

Completeness3/5

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

Given the tool's complexity (36 parameters, nested objects, no output schema), the description is minimal. It clarifies the clearing mechanism but leaves crucial update semantics unspecified (e.g., partial update vs. full replacement). The rich schema descriptions partially offset this, but overall the description is under-specified for such a complex mutation tool.

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 only 47%, leaving over half of parameters without descriptions. The tool description provides a general clearing rule that helps understand array/string parameters, but it doesn't compensate for the many undocumented parameters. Some schema property descriptions already mention clear behavior, so the description's contribution is moderate.

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 the tool's function with specific verb 'Update or clear' and resource 'contact fields', distinguishing it from create/delete siblings. It doesn't explicitly name alternatives but the purpose is unambiguous.

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?

No guidance on when to use this tool versus alternatives like create or delete. The clearing behavior implies use for modifying existing contacts, but there are no explicit exclusions or conditions. Sibling tools exist but are not referenced.

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/sam2kb/m365-mcp'

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