Skip to main content
Glama

list_wiki_nodes

List all wiki nodes in a specified space. Optionally filter by parent node to retrieve children of a specific node.

Instructions

[Official API] List nodes in a Wiki space.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesWiki space ID
parent_node_tokenNoParent node token (optional)

Implementation Reference

  • Handler function that executes the list_wiki_nodes tool logic. Delegates to ctx.getOfficialClient().listWikiNodes(args.space_id, { parentNodeToken: args.parent_node_token }).
    async list_wiki_nodes(args, ctx) {
      return json(await ctx.getOfficialClient().listWikiNodes(args.space_id, { parentNodeToken: args.parent_node_token }));
    },
  • Input schema definition for the list_wiki_nodes tool, registering the name, description, input properties (space_id required, parent_node_token optional).
    {
      name: 'list_wiki_nodes',
      description: '[Official API] List nodes in a Wiki space.',
      inputSchema: {
        type: 'object',
        properties: {
          space_id: { type: 'string', description: 'Wiki space ID' },
          parent_node_token: { type: 'string', description: 'Parent node token (optional)' },
        },
        required: ['space_id'],
      },
    },
  • Client-side implementation that actually calls the Feishu API (UAT-first) to list wiki nodes in a space. Accepts spaceId, optional parentNodeToken and pageToken for pagination.
    async listWikiNodes(spaceId, { parentNodeToken, pageToken } = {}) {
      // UAT-first (v1.3.7): bot identity hits 131006 "wiki space permission
      // denied" for spaces it wasn't explicitly invited to, even when the user
      // has access. listWikiSpaces is already UAT-first; this matches.
      const queryParams = { page_size: '50' };
      if (parentNodeToken) queryParams.parent_node_token = parentNodeToken;
      if (pageToken) queryParams.page_token = pageToken;
      const sdkParams = { page_size: 50 };
      if (parentNodeToken) sdkParams.parent_node_token = parentNodeToken;
      if (pageToken) sdkParams.page_token = pageToken;
      const res = await this._asUserOrApp({
        uatPath: `/open-apis/wiki/v2/spaces/${encodeURIComponent(spaceId)}/nodes`,
        query: queryParams,
        sdkFn: () => this.client.wiki.spaceNode.list({ path: { space_id: spaceId }, params: sdkParams }),
        label: 'listWikiNodes',
      });
      return { items: res.data.items || [], hasMore: res.data.has_more, viaUser: !!res._viaUser };
    },
  • Module exports the schemas and handlers for registration by the MCP server framework.
    module.exports = { schemas, handlers };
Behavior2/5

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

No annotations are present, and the description does not disclose behavioral traits such as pagination, sorting, rate limits, or whether the list is flat or hierarchical. The tool likely performs a read operation, but nothing confirms idempotency or side effects.

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 that efficiently communicates the core function. It is appropriately sized for a straightforward tool, though it could be slightly more descriptive without losing conciseness.

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 of the tool (2 params, no output schema), the description is minimal. It fails to mention important aspects like the nature of the returned data (e.g., list of node IDs or full objects) or any limits, which an agent would need to know for correct invocation.

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 input schema has 100% coverage with descriptions for both parameters. The description adds no extra meaning beyond what is in the schema, so baseline 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 clearly states the action (list nodes) and the resource (Wiki space). The phrase 'Official API' adds authority. However, it does not specify what 'nodes' are (e.g., pages or sections), which could be ambiguous but is mitigated by the tool name and context.

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 get_wiki_node, search_wiki, or move_wiki_node. The description does not indicate prerequisites or typical use scenarios.

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