Skip to main content
Glama
kiwamizamurai

Kibela MCP Server

kibela_unlike_note

Remove your like from a Kibela note by providing its note ID.

Instructions

Unlike a note

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteIdYesNote ID

Implementation Reference

  • Tool definition for 'kibela_unlike_note' with name, description, and inputSchema requiring noteId.
    const UNLIKE_NOTE_TOOL: Tool = {
      name: "kibela_unlike_note",
      description: "Unlike a note",
      inputSchema: {
        type: "object",
        properties: {
          noteId: { type: "string", description: "Note ID" },
        },
        required: ["noteId"],
      },
    };
  • Handler case for 'kibela_unlike_note': executes the UnlikeNote GraphQL mutation with the provided noteId and returns the result.
    case "kibela_unlike_note": {
      const noteId = args.noteId as string;
      const operation = `
        mutation UnlikeNote($input: UnlikeInput!) {
          unlike(input: $input) {
            clientMutationId
            likers(first: 10) {
              nodes {
                id
                account
                realName
              }
            }
          }
        }
      `;
    
      const response = await client.request<UnlikeResponse>(operation, {
        input: { noteId },
      });
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.unlike, null, 2),
          },
        ],
      };
    }
  • src/kibela.ts:206-221 (registration)
    Tool registration: UNLIKE_NOTE_TOOL is listed in the tools array on line 217 and handled via switch case on line 616.
    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,
      ],
    }));
  • UnlikeResponse type definition used by the handler to type the GraphQL response.
    export interface UnlikeResponse {
      unlike: {
        clientMutationId: string;
        likers: {
          nodes: KibelaUser[];
        };
      };
    }
Behavior2/5

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

No behavioral details beyond the basic action. Missing information about idempotency (e.g., what happens if the note is not liked), authorization, or side effects. Annotations are absent, so the description should provide more context.

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?

Extremely concise (two words), which is efficient but may sacrifice completeness. Could be slightly expanded while remaining concise.

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 the simplicity (one param, no output schema), the description is minimal but lacks important context such as idempotency, error conditions, or prerequisites. Additional context would improve completeness.

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% with a clear description for noteId ('Note ID'). The description adds no additional meaning beyond the schema, but since schema is adequate, baseline score of 3 is appropriate.

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 'Unlike a note' clearly states the action (unlike) and resource (note), distinguishing it from the sibling tool 'kibela_like_note'. However, it could be more specific (e.g., 'Remove the current user's like from a note').

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 or when not to use this tool, or alternatives. The context implies it's for removing a like, but there is no explicit instruction or exclusion.

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