Skip to main content
Glama
nulab

Backlog MCP Server

get_users

Retrieve all user accounts from your Backlog project management workspace to manage team access and assign tasks.

Instructions

Returns list of users in the Backlog space

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The getUsersTool function defines the MCP tool 'get_users', including its schema, description, and handler which executes backlog.getUsers() to fetch users from 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(),
      };
    };
  • Defines the input schema for the get_users tool, which takes no parameters.
    const getUsersSchema = buildToolSchema((_t) => ({}));
  • Registers the getUsersTool as part of the 'space' toolset group in the allTools function.
      getSpaceTool(backlog, helper),
      getUsersTool(backlog, helper),
      getMyselfTool(backlog, helper),
    ],
  • Specifies the input schema (empty object), output schema as UserSchema, and important fields for the get_users tool.
    schema: z.object(getUsersSchema(t)),
    outputSchema: UserSchema,
    importantFields: ['userId', 'name', 'roleType', 'lang'],
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it returns a list without detailing behavior. It doesn't cover pagination, sorting, filtering, error conditions, authentication needs, or rate limits, which are critical for a read operation in this context.

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, clear sentence with zero waste—it directly states the tool's function without unnecessary words. It's front-loaded and efficiently communicates the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimal but incomplete. It doesn't address behavioral aspects like return format, pagination, or error handling, which are needed for a read operation in a server with many sibling tools.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter info, which is appropriate here, earning a baseline score above 3 due to the lack of parameters.

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 states the verb ('Returns') and resource ('list of users in the Backlog space'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_myself' (which returns current user) or 'get_project_list' (which returns projects), so it misses full sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context for usage, or compare it to similar tools like 'get_myself' for current user data or 'get_project_list' for project-related user lists, leaving the agent with no usage direction.

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