Skip to main content
Glama

list_ecm_folder

Retrieve the ECM folder contents for a specific Webex room by providing the room ID, enabling streamlined access to shared files and resources.

Instructions

List the ECM folder of a specified room in Webex.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roomIdYesThe ID of the room for which to list the ECM folder.

Implementation Reference

  • Handler function that lists the ECM folder by making a GET request to Webex /room/linkedFolders endpoint with the given roomId.
    const executeFunction = async ({ roomId }) => {
    
      try {
        // Construct the URL with query parameters
        const url = new URL(getWebexUrl('/room/linkedFolders'));
        url.searchParams.append('roomId', roomId);
    
        // Set up headers for the request
        const headers = getWebexHeaders();
    
        // Perform the fetch request
        const response = await fetch(url.toString(), {
          method: 'GET',
          headers
        });
    
        // Check if the response was successful
        if (!response.ok) {
          const errorData = await response.json();
          throw new Error(errorData);
        }
    
        // Parse and return the response data
        const data = await response.json();
        return data;
      } catch (error) {
        console.error('Error listing ECM folder:', error);
        return { error: 'An error occurred while listing the ECM folder.' };
      }
    };
  • Tool schema definition including name 'list_ecm_folder', description, input parameters (roomId: string, required).
    const apiTool = {
      function: executeFunction,
      definition: {
        type: 'function',
        function: {
          name: 'list_ecm_folder',
          description: 'List the ECM folder of a specified room in Webex.',
          parameters: {
            type: 'object',
            properties: {
              roomId: {
                type: 'string',
                description: 'The ID of the room for which to list the ECM folder.'
              }
            },
            required: ['roomId']
          }
        }
      }
    };
  • tools/paths.js:20-20 (registration)
    Path to the list_ecm_folder tool file included in toolPaths array for dynamic discovery.
    'webex-public-workspace/webex-messaging/list-ecm-folder.js',
  • lib/tools.js:7-16 (registration)
    Dynamic tool discovery function that loads apiTool from each path in toolPaths, including list-ecm-folder.js.
    export async function discoverTools() {
      const toolPromises = toolPaths.map(async (file) => {
        const module = await import(`../tools/${file}`);
        return {
          ...module.apiTool,
          path: file,
        };
      });
      return Promise.all(toolPromises);
    }
  • mcpServer.js:87-138 (registration)
    MCP server registration loop that registers each discovered tool (including list_ecm_folder) by calling server.registerTool with name, schema, and wrapper handler.
    for (const tool of tools) {
      const definition = tool.definition?.function;
      if (!definition) {
        console.error(`[MCP Server] Skipping tool with invalid definition:`, tool);
        continue;
      }
    
      try {
        server.registerTool(
          definition.name,
          {
            title: definition.name.replace(/_/g, ' ').replace(/\b\w/g, l => l.toUpperCase()),
            description: definition.description,
            // MCP SDK v1.17.4 requires inputSchema with Zod schemas for parameter validation
            inputSchema: convertJsonSchemaToZod(definition.parameters?.properties || {}, definition.parameters?.required || [])
          },
          async (args) => {
            try {
              // Debug logging to see what we actually receive
              console.error(`[DEBUG] Tool ${definition.name} called with args:`, JSON.stringify(args));
              console.error(`[DEBUG] Args type:`, typeof args);
              console.error(`[DEBUG] Args keys:`, Object.keys(args || {}));
    
              // Handle both function and handler patterns
              const toolFunction = tool.function || tool.handler;
              if (!toolFunction) {
                throw new Error(`Tool ${definition.name} has no function or handler`);
              }
    
              const result = await toolFunction(args);
              return {
                content: [{
                  type: 'text',
                  text: JSON.stringify(result, null, 2)
                }]
              };
            } catch (error) {
              console.error(`[MCP Server] Tool ${definition.name} error:`, error);
              return {
                content: [{
                  type: 'text',
                  text: `Error: ${error.message}`
                }],
                isError: true
              };
            }
          }
        );
      } catch (error) {
        console.error(`[MCP Server] Failed to register tool ${definition.name}:`, error);
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions listing but doesn't cover aspects like pagination, rate limits, authentication requirements, error conditions, or what the output looks like (e.g., folder metadata or contents). This leaves significant gaps for an agent to understand tool behavior.

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, clear sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 no annotations, no output schema, and a simple parameter, the description is incomplete. It lacks details on behavioral traits (e.g., read-only nature, potential side effects), output format, and usage context relative to siblings, making it insufficient for confident tool 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?

Schema description coverage is 100%, so the schema fully documents the single parameter 'roomId'. The description adds no additional meaning beyond implying the room is in Webex, which is already clear from context. This meets the baseline for high schema coverage.

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') and resource ('ECM folder of a specified room in Webex'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_ecm_folder_details' or 'list_rooms', which would be needed for a perfect score.

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_ecm_folder_details' (which might retrieve specific folder details) or 'list_rooms' (which lists rooms rather than folders). The description only states what it does, not when it's appropriate.

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

Related 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/Kashyap-AI-ML-Solutions/webex-messaging-mcp-server'

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