Skip to main content
Glama
Sign In
MCP Teamleader Focus

MCP Teamleader Focus

by growing-pai-git
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

teamleader_list_users

List Teamleader account users to find user IDs for assigning tasks, deals, or ownership fields. Filter by search term and paginate results.

Instructions

List users (co-workers) in the Teamleader account. Use to find user IDs for responsible_user_id / assignee / owner fields.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1)
termNoSearch term filter
page_sizeNoPage size (default: 20, max: 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It conveys read-only list semantics and the meaningful output (user IDs), but it does not disclose pagination behavior, term match scope, or response shape. This is adequate but leaves some behavioral gaps.

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?

Two sentences with no filler. The main purpose is front-loaded, and the user-ID use case is stated in the second sentence. Every sentence earns its place.

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 simple list tool with no required parameters and no output schema, the description provides the resource, account scope, and a clear reason for calling it. Pagination and search parameters are already covered in the schema, so an agent can invoke it correctly with the information given.

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?

The input schema already documents all three parameters with 100% coverage, so the baseline is 3. The description does not add per-parameter details beyond pointing at user-ID lookup, which is useful context but not additional parameter semantics.

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 states a specific verb and resource: 'List users (co-workers) in the Teamleader account.' It also clarifies the intended output by saying the tool is used to find user IDs for responsible_user_id / assignee / owner fields, which distinguishes it from sibling list tools like list_contacts or list_teams.

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?

The description gives a clear use case: 'Use to find user IDs for responsible_user_id / assignee / owner fields.' This tells an agent when to invoke it, though it does not explicitly name alternatives or state when not to use it.

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