Skip to main content
Glama
aikts

Yandex Tracker MCP

by aikts
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

Get All Users

users_get_all
Read-only

Retrieve user accounts registered in the organization, with pagination and field selection to get only needed data. Use to list or filter users efficiently.

Instructions

Get information about user accounts registered in the organization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number to return, default is 1
fieldsNoFields to include in each user; omit to get all. Select only what you need.
per_pageNoThe number of items per page. May be decreased if results exceed context window. If there is a change in per_page argument - retrieval must be started over with page = 1, as the paging could have changed.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hitsNoTotal items matching the request, across all pages. Null if unknown or filtered - then page on until a page comes back empty.
pagesNoTotal pages at the requested `per_page`; this is the last page when it equals `page`. Null together with `hits`.
valuesNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.10.0
    • changedInput schema / properties / fields / description
      Previous value: -"Fields to include in each user. In order to not pollute the context window - select only the fields you need. Not specifying this returns all available fields."New value: +"Fields to include in each user; omit to get all. Select only what you need."
  2. Changed8 schema fields changedv0.8.0
    • addedInput schema / $defs
      Added value: +{
+  "UserFieldsEnum": {
+    "enum": [
+      "uid",
+      "login",
+      "first_name",
+      "last_name",
+      "display",
+      "email",
+      "external",
+      "dismissed"
+    ],
+    "title": "UserFieldsEnum",
+    "type": "string"
+  }
+}
    • addedInput schema / properties / fields
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "$ref": "#/$defs/UserFieldsEnum"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Fields to include in each user. In order to not pollute the context window - select only the fields you need. Not specifying this returns all available fields.",
+  "title": "Fields"
+}
    • addedOutput schema / properties / hits
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Total items matching the request, across all pages. Null if unknown or filtered - then page on until a page comes back empty.",
+  "title": "Hits"
+}
    • addedOutput schema / properties / pages
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Total pages at the requested `per_page`; this is the last page when it equals `page`. Null together with `hits`.",
+  "title": "Pages"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "items": {
-    "$ref": "#/$defs/User"
-  },
-  "title": "Result",
-  "type": "array"
-}
    • addedOutput schema / properties / values
      Added value: +{
+  "items": {
+    "$ref": "#/$defs/User"
+  },
+  "title": "Values",
+  "type": "array"
+}
    • removedOutput schema / required
      Removed value: -[
-  "result"
-]
    • changedOutput schema / title
      Previous value: -"users_get_allOutput"New value: +"PaginatedResult[User]"
  3. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

The readOnlyHint annotation already communicates that this is a read-only operation, and the description adds little beyond restating that. It does not disclose pagination behavior, result limits, or any other operational traits, aside from the nominal scoping to organization-registered accounts.

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 single concise sentence with no wasted words and is easy to parse. However, it is somewhat generic ('Get information') and could have used the space to add scope or sibling differentiation without becoming verbose.

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?

The presence of an output schema and well-described parameters covers much of what an agent needs to make a valid call. Still, the description fails to guide selection among closely related user tools, and the pagination reset behavior is only visible in the schema rather than highlighted as a usage consideration.

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%, so the description does not need to explain parameters. The schema already documents page, fields, and per_page with meaningful guidance, including the context-window note. The description adds no parameter-level meaning, but the baseline of 3 is appropriate given full schema coverage.

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 identifies a specific verb and resource: getting information about user accounts. However, it does not differentiate from sibling tools like users_search, user_get, or user_get_current, so the agent must rely on the tool name to infer it is a list-all operation.

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 usage guidance is provided. The description does not state when to use this tool over users_search or user_get, nor does it mention pagination as a reason to use this tool versus alternatives. The agent is left to infer context from the name and parameter schema.

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/aikts/yandex-tracker-mcp'

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