Skip to main content
Glama
kiwamizamurai

Kibela MCP Server

kibela_get_group_folders

Get folders in a specified Kibela group by group ID and optional parent folder ID to navigate the group's folder hierarchy.

Instructions

Get folders in a group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupIdYesGroup ID
parentFolderIdNoParent folder ID

Implementation Reference

  • Handler for kibela_get_group_folders. Extracts groupId and optional parentFolderId from args, executes a GraphQL query (GetGroupFolders) to fetch folders (with nested notes) for the given group, and returns the result.
    case "kibela_get_group_folders": {
      const { groupId, parentFolderId } = args as {
        groupId: string;
        parentFolderId?: string;
      };
    
      const operation = `
        query GetGroupFolders($groupId: ID!, $parentFolderId: ID) {
          group(id: $groupId) {
            folders(first: 30, active: true, parentFolderId: $parentFolderId) {
              nodes {
                id
                name
                fullName
                path
                canBeManaged
                parent {
                  id
                  name
                }
                notes(first: 10, active: true, orderBy: { field: CONTENT_UPDATED_AT, direction: DESC }) {
                  nodes {
                    id
                    title
                    contentUpdatedAt
                    publishedAt
                    author {
                      account
                      realName
                    }
                  }
                }
              }
            }
          }
        }
      `;
    
      const response = await client.request<GroupFoldersResponse>(operation, {
        groupId,
        parentFolderId,
      });
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.group.folders.nodes, null, 2),
          },
        ],
      };
    }
  • Tool definition for kibela_get_group_folders. Defines inputSchema with groupId (required) and parentFolderId (optional).
    const GET_GROUP_FOLDERS_TOOL: Tool = {
      name: "kibela_get_group_folders",
      description: "Get folders in a group",
      inputSchema: {
        type: "object",
        properties: {
          groupId: { type: "string", description: "Group ID" },
          parentFolderId: { type: "string", description: "Parent folder ID" },
        },
        required: ["groupId"],
      },
  • Type definition for GroupFoldersResponse, representing the shape of the GraphQL response (group with folders containing notes).
    export interface GroupFoldersResponse {
      group: {
        folders: {
          nodes: (KibelaFolder & {
            notes: {
              nodes: KibelaNote[];
            };
          })[];
        };
      };
    }
  • src/kibela.ts:206-220 (registration)
    Tool registration via ListToolsRequestSchema handler, where GET_GROUP_FOLDERS_TOOL (line 212) is included in the list of available tools.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        SEARCH_NOTES_TOOL,
        GET_MY_NOTES_TOOL,
        GET_NOTE_CONTENT_TOOL,
        GET_GROUPS_TOOL,
        GET_GROUP_FOLDERS_TOOL,
        GET_GROUP_NOTES_TOOL,
        GET_FOLDER_NOTES_TOOL,
        GET_USERS_TOOL,
        LIKE_NOTE_TOOL,
        UNLIKE_NOTE_TOOL,
        GET_RECENTLY_VIEWED_NOTES_TOOL,
        GET_NOTE_FROM_PATH_TOOL,
      ],
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only says 'Get folders in a group', omitting details like whether folders are recursive, permissions required, pagination, or return structure. Essential behavior is missing.

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 concise but at the expense of completeness. It is appropriately short for a simple tool, but lacks necessary context, making it under-specified.

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 no output schema and minimal annotations, the description fails to explain what the tool returns (e.g., folder list with fields), how parentFolderId affects results, or any filters. Sibling tools don't compensate.

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?

Both parameters are described in the input schema (100% coverage). The description adds no additional meaning beyond the schema, achieving the baseline score of 3.

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 action (Get) and resource (folders) within a group. It differentiates from sibling tools like kibela_get_group_notes by specifying 'folders', though it could be more precise about the folder hierarchy given the parentFolderId parameter.

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 alternatives such as kibela_get_folder_notes or kibela_get_group_notes. The description does not mention prerequisites, context, or exclusions.

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/kiwamizamurai/mcp-kibela-server'

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