Skip to main content
Glama
nulab

Backlog MCP Server

get_space_activities

Retrieve a list of space activities from your Backlog project management tool, filterable by activity type, ID range, count, sort order, and organization.

Instructions

Returns list of space activities

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activityTypeIdNoActivity type IDs
minIdNoMinimum activity ID
maxIdNoMaximum activity ID
countNoNumber of activities to retrieve
orderNoSort order
organizationNoOptional organization name. Use list_organizations to inspect available organizations.

Implementation Reference

  • The main tool handler function that defines the 'get_space_activities' tool. It accepts activityTypeId (array of activity types), minId, maxId, count (1-100), and order (asc/desc) parameters and calls backlog.getSpaceActivities() to return a list of space activities.
    export const getSpaceActivitiesTool = (
      backlog: Backlog,
      { t }: TranslationHelper
    ): ToolDefinition<
      ReturnType<typeof getSpaceActivitiesSchema>,
      (typeof ActivitySchema)['shape']
    > => {
      return {
        name: 'get_space_activities',
        description: t(
          'TOOL_GET_SPACE_ACTIVITIES_DESCRIPTION',
          'Returns list of space activities'
        ),
        schema: z.object(getSpaceActivitiesSchema(t)),
        outputSchema: ActivitySchema,
        handler: async ({ activityTypeId, minId, maxId, count, order }) =>
          backlog.getSpaceActivities({
            activityTypeId,
            minId,
            maxId,
            count,
            order,
          }),
      };
    };
  • Input schema definition for 'get_space_activities' using buildToolSchema. Defines parameters: activityTypeId (array of ActivityTypeSchema), minId (number), maxId (number), count (number 1-100), order (enum 'asc'|'desc').
    const getSpaceActivitiesSchema = buildToolSchema((t) => ({
      activityTypeId: z
        .array(ActivityTypeSchema)
        .optional()
        .describe(
          t('TOOL_GET_SPACE_ACTIVITIES_ACTIVITY_TYPE_ID', 'Activity type IDs')
        ),
      minId: z
        .number()
        .optional()
        .describe(t('TOOL_GET_SPACE_ACTIVITIES_MIN_ID', 'Minimum activity ID')),
      maxId: z
        .number()
        .optional()
        .describe(t('TOOL_GET_SPACE_ACTIVITIES_MAX_ID', 'Maximum activity ID')),
      count: z
        .number()
        .min(1)
        .max(100)
        .optional()
        .describe(
          t('TOOL_GET_SPACE_ACTIVITIES_COUNT', 'Number of activities to retrieve')
        ),
      order: z
        .enum(['asc', 'desc'])
        .optional()
        .describe(t('TOOL_GET_SPACE_ACTIVITIES_ORDER', 'Sort order')),
    }));
  • ActivitySchema - the output schema for space activities. Contains id, project (ProjectSchema), type (ActivityTypeSchema), content, notifications, createdUser, and created fields.
    export const ActivitySchema = z.object({
      id: z.number(),
      project: ProjectSchema,
      type: ActivityTypeSchema,
      content: z.any(),
      notifications: z.array(z.any()),
      createdUser: UserSchema,
      created: z.string(),
    });
  • ActivityTypeSchema - enum used for activityTypeId input parameter and the type field in ActivitySchema. Defines all activity types (IssueCreated, IssueUpdated, GitPushed, etc.).
    export const ActivityTypeSchema = z.nativeEnum({
      Undefined: -1,
      IssueCreated: 1,
      IssueUpdated: 2,
      IssueCommented: 3,
      IssueDeleted: 4,
      WikiCreated: 5,
      WikiUpdated: 6,
      WikiDeleted: 7,
      FileAdded: 8,
      FileUpdated: 9,
      FileDeleted: 10,
      SvnCommitted: 11,
      GitPushed: 12,
      GitRepositoryCreated: 13,
      IssueMultiUpdated: 14,
      ProjectUserAdded: 15,
      ProjectUserRemoved: 16,
      NotifyAdded: 17,
      PullRequestAdded: 18,
      PullRequestUpdated: 19,
      PullRequestCommented: 20,
      PullRequestMerged: 21,
      MilestoneCreated: 22,
      MilestoneUpdated: 23,
      MilestoneDeleted: 24,
      ProjectGroupAdded: 25,
      ProjectGroupDeleted: 26,
    });
  • Registration: getSpaceActivitiesTool is imported and included in the 'space' toolset within the allTools() function, making it available as part of the Backlog MCP tool collection.
    import { getSpaceActivitiesTool } from './getSpaceActivities.js';
    import { getUserStarsCountTool } from './getUserStarsCount.js';
    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),
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only says 'returns list,' omitting important details like read-only nature, pagination (despite count parameter), or sorting behavior (order parameter present but not explained). The tool is likely safe, but the description fails to confirm that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (one sentence), which is minimal but not excessively wasteful. However, it lacks critical details that could be added concisely, such as the scope (e.g., 'in the current space') or typical use.

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 6 parameters and no output schema, the description should clarify what 'space activities' are and provide context (e.g., 'activity types' are defined elsewhere). It is insufficient for an agent to fully understand the tool's capabilities or output format.

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 schema already documents all parameters. The description adds no additional semantics beyond the schema's parameter descriptions, meeting the baseline for well-documented schema.

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 a list of space activities, which is specific enough to distinguish it from similar tools like get_issues or get_projects. However, 'space activities' could be more precise, e.g., 'activities in a specific space.'

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 on when to use this tool versus other get_* siblings (e.g., get_issues for tasks, get_projects for projects). The context signals show many similar tools, but the description provides no differentiation or context.

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