Skip to main content
Glama

delete_page

Remove a page from your Logseq knowledge graph by specifying its path or name to manage your workspace content.

Instructions

페이지 삭제

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes삭제할 페이지 경로 또는 이름

Implementation Reference

  • MCP tool handler for 'delete_page': validates input using DeletePageSchema, calls GraphService.deletePage(path), and returns a success message.
    case 'delete_page': {
      const { path } = DeletePageSchema.parse(args);
      await graph.deletePage(path);
      return {
        content: [{ type: 'text', text: `페이지 삭제 완료: ${path}` }],
      };
    }
  • Zod schema defining the input for delete_page tool: requires a 'path' string with maximum length limit.
    const DeletePageSchema = z.object({
      path: z.string().max(MAX_PATH_LENGTH).describe('삭제할 페이지 경로 또는 이름'),
    });
  • src/index.ts:158-168 (registration)
    Tool registration in TOOLS array: defines name 'delete_page', description, and inputSchema for MCP server.
    {
      name: 'delete_page',
      description: '페이지 삭제',
      inputSchema: {
        type: 'object' as const,
        properties: {
          path: { type: 'string', description: '삭제할 페이지 경로 또는 이름' },
        },
        required: ['path'],
      },
    },
  • Core deletion logic in GraphService: resolves the full file path, performs security checks, and deletes the page file using fs.unlink.
    async deletePage(pathOrName: string): Promise<void> {
      const filePath = await this.resolvePath(pathOrName);
      await this.checkSymlink(filePath); // 보안: 심링크 공격 방지
      await unlink(filePath);
    }
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. '페이지 삭제' only indicates a destructive operation but provides no information about permissions required, whether deletion is permanent or reversible, what happens to linked content, rate limits, or error conditions. For a destructive operation with zero annotation coverage, this is critically insufficient.

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?

While technically concise with just two words, this represents under-specification rather than effective brevity. The description fails to provide necessary context for a destructive operation. Every word should earn its place, but here the minimal content fails to adequately describe the tool's purpose and behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive operation with no annotations and no output schema, the description is completely inadequate. It doesn't explain what constitutes a 'page' in this context, what the deletion entails, whether there are confirmation steps, what the response looks like, or any error conditions. Given the complexity of a delete operation and the lack of structured documentation, this description fails to provide necessary context.

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?

The schema description coverage is 100%, with the single parameter 'path' clearly documented as '삭제할 페이지 경로 또는 이름' (path or name of page to delete). The description adds no additional parameter information beyond what the schema already provides. With complete schema coverage, the 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 '페이지 삭제' (delete page) is a tautology that merely restates the tool name in Korean. It doesn't specify what type of page or resource is being deleted, nor does it distinguish this tool from potential alternatives like 'update_page' or other deletion operations. While the verb 'delete' is clear, the description lacks any additional context about the resource being operated on.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides absolutely no guidance about when to use this tool versus alternatives. With multiple sibling tools including 'update_page', 'read_page', and 'list_pages', there's no indication of when deletion is appropriate versus modification or retrieval. No prerequisites, constraints, or comparison to other tools are mentioned.

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/dearcloud09/logseq-mcp'

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