Skip to main content
Glama
nulab

Backlog MCP Server

get_users

Retrieve all users in your Backlog space. Specify an optional organization to filter results.

Instructions

Returns list of users in the Backlog space

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationNoOptional organization name. Use list_organizations to inspect available organizations.

Implementation Reference

  • The actual handler function for the 'get_users' tool. It calls backlog.getUsers() to return the list of users in the Backlog space.
    export const getUsersTool = (
      backlog: Backlog,
      { t }: TranslationHelper
    ): ToolDefinition<
      ReturnType<typeof getUsersSchema>,
      (typeof UserSchema)['shape']
    > => {
      return {
        name: 'get_users',
        description: t(
          'TOOL_GET_USERS_DESCRIPTION',
          'Returns list of users in the Backlog space'
        ),
        schema: z.object(getUsersSchema(t)),
        outputSchema: UserSchema,
        importantFields: ['userId', 'name', 'roleType', 'lang'],
        handler: async () => backlog.getUsers(),
      };
    };
  • The output schema (UserSchema) defining the shape of each user object returned by get_users (id, userId, name, roleType, lang, mailAddress, lastLoginTime).
    export const UserSchema = z.object({
      id: z.number(),
      userId: z.string(),
      name: z.string(),
      roleType: RoleTypeSchema,
      lang: LanguageSchema,
      mailAddress: z.string(),
      lastLoginTime: z.string(),
    });
  • Input schema for get_users — empty object, meaning no input parameters are required.
    const getUsersSchema = buildToolSchema((_t) => ({}));
  • Import and registration of getUsersTool in the 'space' toolset within the allTools function.
    import { getUsersTool } from './getUsers.js';
    import { getUserRecentUpdatesTool } from './getUserRecentUpdates.js';
    import { getWatchingListCountTool } from './getWatchingListCount.js';
    import { getWatchingListItemsTool } from './getWatchingListItems.js';
    import { addWatchingTool } from './addWatching.js';
    import { updateWatchingTool } from './updateWatching.js';
    import { deleteWatchingTool } from './deleteWatching.js';
    import { markWatchingAsReadTool } from './markWatchingAsRead.js';
    import { getWikiTool } from './getWiki.js';
    import { getWikiPagesTool } from './getWikiPages.js';
    import { getWikisCountTool } from './getWikisCount.js';
    import { markNotificationAsReadTool } from './markNotificationAsRead.js';
    import { resetUnreadNotificationCountTool } from './resetUnreadNotificationCount.js';
    import { updateIssueTool } from './updateIssue.js';
    import { updateProjectTool } from './updateProject.js';
    import { updatePullRequestTool } from './updatePullRequest.js';
    import { updatePullRequestCommentTool } from './updatePullRequestComment.js';
    import { getDocumentTool } from './getDocument.js';
    import { getDocumentsTool } from './getDocuments.js';
    import { getDocumentTreeTool } from './getDocumentTree.js';
    import { getVersionMilestoneListTool } from './getVersionMilestoneList.js';
    import { addVersionMilestoneTool } from './addVersionMilestone.js';
    import { updateVersionMilestoneTool } from './updateVersionMilestone.js';
    import { deleteVersionTool } from './deleteVersion.js';
    import { addDocumentTool } from './addDocument.js';
    
    export const allTools = (
      backlog: Backlog,
      helper: TranslationHelper
    ): ToolsetGroup => {
      return {
        toolsets: [
          {
            name: 'space',
            description:
              'Tools for managing Backlog space settings and general information.',
            enabled: false,
            tools: [
              getSpaceTool(backlog, helper),
              getSpaceActivitiesTool(backlog, helper),
              getUsersTool(backlog, helper),
              getUserStarsCountTool(backlog, helper),
  • The buildToolSchema helper used to define the input schema for get_users.
    export const buildToolSchema = <T extends z.ZodRawShape>(
      fn: (t: TranslationHelper['t']) => T
    ) => fn;
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as authentication requirements, rate limits, pagination, or default behavior when the optional parameter is omitted. The description only states the basic operation.

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?

The description is a single sentence that immediately conveys the tool's purpose without any unnecessary words. It is well-structured and front-loaded.

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?

For a simple list tool with one optional parameter and no output schema, the description covers the main purpose. However, it lacks details on pagination or default scope, which would be helpful for complete understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage for the single optional parameter. The description adds value by suggesting to use list_organizations to inspect available organization names, which goes beyond the schema's type definition.

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 clearly states that the tool returns a list of users, specifying the resource ('users') and scope ('in the Backlog space'). This distinguishes it from other get_* tools that return different resources like issues or projects.

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 is provided on when to use this tool versus alternatives such as get_myself. The description lacks explicit context about prerequisites or preferred use cases.

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/nulab/backlog-mcp-server'

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