Skip to main content
Glama
kiwamizamurai

Kibela MCP Server

kibela_get_folder_notes

Retrieve all notes from a specified folder in Kibela using folder ID. Optionally set a limit on the number of notes returned.

Instructions

Get notes in a folder

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderIdYesFolder ID
limitNoNumber of notes to fetch (default 100)

Implementation Reference

  • Handler for kibela_get_folder_notes: extracts folderId and optional limit (default 100), executes a GraphQL query GetFolderNotes against the folder's notes sorted by content updated time, and returns the notes as JSON.
    case "kibela_get_folder_notes": {
      const { folderId, limit = 100 } = args as { folderId: string; limit?: number };
    
      const operation = `
        query GetFolderNotes($folderId: ID!, $limit: Int!) {
          folder(id: $folderId) {
            notes(first: $limit, active: true, orderBy: { field: CONTENT_UPDATED_AT, direction: DESC }) {
              nodes {
                id
                title
                contentUpdatedAt
                publishedAt
                author {
                  account
                  realName
                }
              }
            }
          }
        }
      `;
    
      const response = await client.request<FolderNotesResponse>(operation, { folderId, limit });
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.folder.notes.nodes, null, 2),
          },
        ],
      };
    }
  • Schema definition for kibela_get_folder_notes tool, declaring folderId (required string) and limit (optional number, default 100) as input parameters.
    const GET_FOLDER_NOTES_TOOL: Tool = {
      name: "kibela_get_folder_notes",
      description: "Get notes in a folder",
      inputSchema: {
        type: "object",
        properties: {
          folderId: { type: "string", description: "Folder ID" },
          limit: {
            type: "number",
            description: "Number of notes to fetch (default 100)",
            default: 100,
          },
        },
        required: ["folderId"],
      },
    };
  • TypeScript type definition for the GraphQL response of GetFolderNotes query, describing the shape of folder notes data.
    export interface FolderNotesResponse {
      folder: {
        notes: {
          nodes: {
            id: string;
            title: string;
            contentUpdatedAt: string;
            publishedAt: string;
            author: {
              account: string;
              realName: string;
            };
          }[];
        };
      };
    }
  • src/kibela.ts:206-221 (registration)
    Registration of GET_FOLDER_NOTES_TOOL in the list of available tools exposed via ListToolsRequestSchema handler.
    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?

No annotations are provided, and the description does not disclose behavioral traits such as whether it returns note content metadata, pagination beyond the limit parameter, or sorting behavior. It is too terse for a read operation.

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 a single sentence with no wasted words. However, it is slightly under-specified for completeness.

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?

No output schema is provided, and the description does not explain what is returned (e.g., full notes or summaries). Missing details on ordering, pagination behavior, and whether subfolder notes are included.

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?

Input schema covers 100% of parameters with descriptions. The description adds no extra meaning beyond the schema, so baseline is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get notes in a folder' clearly indicates retrieving notes from a folder, but lacks scope details. It does not distinguish from sibling tools like kibela_get_group_notes or kibela_search_notes.

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 (e.g., search_notes, get_group_notes). The description does not clarify if this returns only top-level notes or recursively.

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