Skip to main content
Glama

List Teams Chats

list_chats
Read-only

Lists your Microsoft Teams one-to-one, group, and meeting chats with topic or member names, last-message time and sender, sorted by last-message time descending.

Instructions

List your Teams chats (1:1, group, and meeting chats), most recent message first. Each line names the chat by its topic or its members and shows when the last message was sent and by whom. Note: the self-chat (notes to self) is not listed here — use chat_id '48:notes' to send to it directly.

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": "list_chats"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoNumber of chats to return (default: 25, max 50; with since, every match unless set). Graph may return fewer per page when member names are included; use fetch_all_pages for more.
sinceNoOnly chats whose last message is after this ISO 8601 time with a time zone, e.g. 2026-10-01T00:00:00Z. Reads pages until it reaches an older chat (at most 20 pages) and returns every match unless top is set. Chats with no messages are skipped.
fetch_all_pagesNoFetch all pages of results (max 50 pages)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds real value on top by disclosing the return shape ('each line names the chat by its topic or its members and shows when the last message was sent and by whom') and the exclusion of the notes-to-self chat. It does not discuss pagination behavior, though the schema does.

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?

Three sentences, front-loaded with the core action and ordering, then output format, then the exception. No filler and every sentence provides information an agent needs.

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 read-only three-parameter list tool with no output schema, the description covers what is returned, in what order, and one important omission. Pagination and truncation behavior live only in the schema, so completeness stops just short of ideal.

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%, including the subtle interplay between top and since and the fetch_all_pages option, so the schema carries parameter meaning. The description adds nothing about parameters beyond the self-chat note, making the baseline 3 appropriate.

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?

States a specific verb and resource with scope qualifiers — 'List your Teams chats (1:1, group, and meeting chats)' — plus an explicit ordering rule ('most recent message first'). An agent can tell this apart from message-listing siblings, though it never names list_chat_messages as the alternative for reading messages.

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

Usage Guidelines4/5

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

Gives clear context for use and one concrete exception with a workaround: the self-chat is excluded and the agent should target chat_id '48:notes' directly. It lacks explicit when-not guidance or a named alternative tool, so it falls short of a 5.

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