Skip to main content
Glama
nulab

Backlog MCP Server

get_user_stars_count

Count the stars a user received within a date range. Specify user ID and optional dates to get the star count.

Instructions

Returns the count of stars received by a user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdYesUser ID
sinceNoCount stars received after this date (yyyy-MM-dd)
untilNoCount stars received before this date (yyyy-MM-dd)
organizationNoOptional organization name. Use list_organizations to inspect available organizations.

Implementation Reference

  • The handler function that executes the 'get_user_stars_count' tool logic. It calls backlog.getUserStarsCount with userId, since, and until parameters.
      handler: async ({ userId, since, until }) =>
        backlog.getUserStarsCount(userId, { since, until }),
    };
  • Input schema defining the tool's parameters: userId (number, required), since (string, optional), until (string, optional).
    const getUserStarsCountSchema = buildToolSchema((t) => ({
      userId: z
        .number()
        .describe(t('TOOL_GET_USER_STARS_COUNT_USER_ID', 'User ID')),
      since: z
        .string()
        .optional()
        .describe(
          t(
            'TOOL_GET_USER_STARS_COUNT_SINCE',
            'Count stars received after this date (yyyy-MM-dd)'
          )
        ),
      until: z
        .string()
        .optional()
        .describe(
          t(
            'TOOL_GET_USER_STARS_COUNT_UNTIL',
            'Count stars received before this date (yyyy-MM-dd)'
          )
        ),
    }));
  • Output schema (StarCountSchema) defining the response shape: an object with a count (number) field.
    export const StarCountSchema = z.object({
      count: z.number(),
    });
  • Registration of the getUserStarsCountTool in the 'space' toolset within the allTools function.
    getUserStarsCountTool(backlog, helper),
  • Import statement for getUserStarsCountTool in the tools registration file.
    import { getUserStarsCountTool } from './getUserStarsCount.js';
Behavior2/5

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

The description indicates a read operation but does not elaborate on side effects, idempotency, or what 'stars' refers to (e.g., stars on issues, pull requests). With no annotations, the description carries the full burden and falls short.

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 extremely concise at one sentence (7 words) and front-loaded. It could be slightly more informative without harming conciseness.

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?

With no output schema and minimal description, the tool lacks context about what the count represents, date range applicability, and organization scope. The sibling tools do not clarify this, leaving agents underinformed.

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 baseline is 3. The description adds no new meaning beyond the schema, which already explains each parameter adequately.

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 tool returns the count of stars for a user, distinguishing it from siblings like count_issues and count_notifications. However, it does not mention the optional date range parameters, which would enhance clarity.

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 count_issues or get_pull_requests_count. The description lacks context for typical usage scenarios.

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