Skip to main content
Glama

update_wiki_node

Renames a wiki node in a given space using the node token and new title. Only the title is updated; content is managed by other tools.

Instructions

[Official API] Rename a Wiki node (only title is updatable via the wiki API; the underlying resource content is edited via docx/bitable/sheet tools).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesWiki space ID
node_tokenYesWiki node token (wikcnXXX)
titleYesNew title

Implementation Reference

  • The handler function for the 'update_wiki_node' tool. Calls ctx.getOfficialClient().updateWikiNodeTitle(args.space_id, args.node_token, args.title).
    async update_wiki_node(args, ctx) {
      return json(await ctx.getOfficialClient().updateWikiNodeTitle(args.space_id, args.node_token, args.title));
    },
  • The schema/input definition for the 'update_wiki_node' tool defining its name, description, and inputSchema (space_id, node_token, title).
    {
      name: 'update_wiki_node',
      description: '[Official API] Rename a Wiki node (only `title` is updatable via the wiki API; the underlying resource content is edited via docx/bitable/sheet tools).',
      inputSchema: {
        type: 'object',
        properties: {
          space_id: { type: 'string', description: 'Wiki space ID' },
          node_token: { type: 'string', description: 'Wiki node token (wikcnXXX)' },
          title: { type: 'string', description: 'New title' },
        },
        required: ['space_id', 'node_token', 'title'],
      },
    },
  • src/server.js:37-57 (registration)
    Tool registration: TOOL_MODULES array includes require('./tools/wiki'), TOOLS = schemas flattened, HANDLERS = map of handler name to function. The update_wiki_node handler is registered via HANDLERS lookup on line 396.
    const TOOL_MODULES = [
      require('./tools/bitable'),
      require('./tools/calendar'),
      require('./tools/contacts'),
      require('./tools/diagnostics'),
      require('./tools/docs'),
      require('./tools/drive'),
      require('./tools/events'),
      require('./tools/groups'),
      require('./tools/im-read'),
      require('./tools/messaging-bot'),
      require('./tools/messaging-user'),
      require('./tools/okr'),
      require('./tools/profile'),
      require('./tools/tasks'),
      require('./tools/uploads'),
      require('./tools/wiki'),
    ];
    
    const TOOLS = TOOL_MODULES.flatMap((m) => m.schemas);
    const HANDLERS = Object.fromEntries(TOOL_MODULES.flatMap((m) => Object.entries(m.handlers)));
  • The client-side helper method updateWikiNodeTitle(spaceId, nodeToken, title) that calls the Feishu API endpoint /open-apis/wiki/v2/spaces/{spaceId}/nodes/{nodeToken}/update_title using _asUserOrApp for UAT-first execution.
    // Rename a wiki node. Feishu's SDK exposes this as updateTitle (the
    // underlying API is /open-apis/wiki/v2/spaces/{space_id}/nodes/{token}/update_title).
    async updateWikiNodeTitle(spaceId, nodeToken, title) {
      if (!spaceId) throw new Error('updateWikiNodeTitle: spaceId is required');
      if (!nodeToken) throw new Error('updateWikiNodeTitle: nodeToken is required');
      if (!title) throw new Error('updateWikiNodeTitle: title is required');
      const data = { title };
      const res = await this._asUserOrApp({
        uatPath: `/open-apis/wiki/v2/spaces/${encodeURIComponent(spaceId)}/nodes/${encodeURIComponent(nodeToken)}/update_title`,
        method: 'POST',
        body: data,
        sdkFn: () => this.client.wiki.spaceNode.updateTitle({ path: { space_id: spaceId, node_token: nodeToken }, data }),
        label: 'updateWikiNodeTitle',
      });
      return { ok: res.code === 0, viaUser: !!res._viaUser, fallbackWarning: res._fallbackWarning || null };
    },
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that only title can be updated and that content is edited via other tools, but does not mention error conditions or idempotency. Still, it is transparent about limitations.

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

Conciseness5/5

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

The description is a single sentence that is front-loaded with the key action, no wasted words.

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

Completeness5/5

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

Given the tool's simplicity (3 required params, no output schema, no nested objects), the description fully covers what the agent needs to know to use it correctly.

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 marginal value by clarifying that title is the only updatable field, but the schema already explains each parameter.

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

Purpose5/5

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

The description clearly states it renames a Wiki node and specifies that only 'title' is updatable, distinguishing it from sibling tools like copy_wiki_node, move_wiki_node, etc.

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

Usage Guidelines5/5

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

The description explicitly provides when-to-use by stating only title is updatable and directs to other tools for content editing, giving clear alternatives.

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/EthanQC/feishu-user-plugin'

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