Skip to main content
Glama
kiwamizamurai

Kibela MCP Server

kibela_like_note

Like a note in Kibela by specifying its note ID.

Instructions

Like a note

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteIdYesNote ID

Implementation Reference

  • Schema/definition of the 'kibela_like_note' tool. Defines its name, description, and input schema requiring a 'noteId' string.
    const LIKE_NOTE_TOOL: Tool = {
      name: "kibela_like_note",
      description: "Like a note",
      inputSchema: {
        type: "object",
        properties: {
          noteId: { type: "string", description: "Note ID" },
        },
        required: ["noteId"],
      },
    };
  • src/kibela.ts:206-221 (registration)
    Registration of the LIKE_NOTE_TOOL in the ListToolsRequestSchema handler, making it available to the client.
    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,
      ],
    }));
  • Handler logic for 'kibela_like_note' tool. Extracts noteId from args, executes a GraphQL 'like' mutation via the Kibela API, and returns the likers list.
    case "kibela_like_note": {
      const noteId = args.noteId as string;
      const operation = `
        mutation LikeNote($input: LikeInput!) {
          like(input: $input) {
            clientMutationId
            likers(first: 3) {
              nodes {
                id
                account
                realName
              }
            }
          }
        }
      `;
    
      const response = await client.request<LikeResponse>(operation, {
        input: { noteId },
      });
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.like, null, 2),
          },
        ],
      };
    }
  • TypeScript interface for the GraphQL response type 'LikeResponse' used by the like mutation.
    export interface LikeResponse {
      like: {
        clientMutationId: string;
        likers: {
          nodes: KibelaUser[];
        };
      };
    }
Behavior1/5

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

With no annotations, the description must convey behavioral traits, but it offers none. It does not state side effects, idempotency, permissions, or return behavior. The description adds no value beyond the tool name.

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

Conciseness2/5

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

At three words, the description is concise but under-specified. It fails to provide necessary context and does not earn its place with informative content.

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?

For a simple action tool, the description is inadequate. It omits crucial details like what 'liking' entails, effects, error conditions, and any prerequisites. The description is far from complete given the tool's role.

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 coverage is 100% for the single required parameter noteId. The schema already describes it as a string with description 'Note ID'. The tool description adds no additional meaning, so baseline score of 3 is appropriate.

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

Purpose2/5

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

The description 'Like a note' essentially restates the tool name 'like_note' without adding specificity or distinguishing it from the sibling 'kibela_unlike_note'. It is a tautology rather than a clear statement of purpose.

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 like 'kibela_unlike_note' or other tools. The agent receives no context for appropriate invocation.

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