Skip to main content
Glama
InditexTech

MCP Microsoft Teams Server

by InditexTech

list_threads

List threads in a Microsoft Teams channel with pagination to navigate through multiple pages of results.

Instructions

List threads in channel with pagination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of items to retrieve or page size
cursorNoPagination cursor for the next page of results

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorYesCursor to retrieve the next page of messages.
limitYesPage limit, maximum number of items to retrieve
totalYesTotal items available for retrieval
itemsYesList of channel messages or threads

Implementation Reference

  • MCP tool handler for 'list_threads' - receives limit and cursor parameters, delegates to TeamsClient.read_threads()
    @mcp.tool(name="list_threads", description="List threads in channel with pagination")
    async def list_threads(
        ctx: Context,
        limit: int = Field(
            description="Maximum number of items to retrieve or page size", default=50
        ),
        cursor: str | None = Field(
            description="Pagination cursor for the next page of results", default=None
        ),
    ) -> PagedTeamsMessages:
        await ctx.debug(f"list_threads with cursor={cursor} and limit={limit}")
        client = _get_teams_client(ctx)
        return await client.read_threads(limit, cursor)
Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It only states 'list' operation but fails to mention if it's read-only, required authentication, or how channel context is determined. This is a significant gap for a tool with no annotations.

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?

Single sentence, front-loaded with key information: action, resource, scope, and feature. No unnecessary words.

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?

Output schema exists, so return values need not be explained. However, the description lacks context on how the channel is specified, which could be ambiguous. For a simple 2-parameter tool, it is minimally complete but could be improved.

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 100% with both parameters clearly described. The description adds no extra meaning beyond 'pagination', which is already implied by the parameter names and schemas.

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?

Description clearly states verb 'list', resource 'threads', scope 'in channel', and feature 'pagination'. It effectively distinguishes from siblings like 'read_thread' (single thread) and 'start_thread' (create).

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?

Implies usage for listing threads, but no explicit guidance on when to use vs alternatives like 'read_thread' for details or 'list_members' for members. No exclusions mentioned.

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/InditexTech/mcp-teams-server'

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