Skip to main content
Glama

create_ecm_folder

Automate ECM folder configuration in Webex by linking folders to specific rooms, associating content URLs, and setting default folder preferences.

Instructions

Create an ECM folder configuration in Webex.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentUrlYesThe URL of the content associated with the folder.
defaultFolderNoWhether this folder is the default folder.
displayNameYesThe display name for the folder.
driveIdYesThe ID of the drive where the folder is located.
itemIdYesThe ID of the item (folder) to be linked.
roomIdYesThe ID of the room where the folder will be linked.

Implementation Reference

  • The executeFunction is the core handler that sends a POST request to Webex API endpoint '/room/linkedFolders' to create the ECM folder configuration with the provided parameters.
    const executeFunction = async ({ roomId, contentUrl, displayName, driveId, itemId, defaultFolder = false }) => {
    
      const url = getWebexUrl('/room/linkedFolders');
    
      const headers = getWebexJsonHeaders();
    
      const body = JSON.stringify({
        roomId,
        contentUrl,
        displayName,
        driveId,
        itemId,
        defaultFolder
      });
    
      try {
        const response = await fetch(url, {
          method: 'POST',
          headers,
          body
        });
    
        if (!response.ok) {
          const errorData = await response.json();
          throw new Error(errorData);
        }
    
        const data = await response.json();
        return data;
      } catch (error) {
        console.error('Error creating ECM folder configuration:', error);
        return { error: 'An error occurred while creating the ECM folder configuration.' };
      }
    };
  • The tool schema defining the name 'create_ecm_folder', description, input parameters with types and descriptions, and required fields.
        name: 'create_ecm_folder',
        description: 'Create an ECM folder configuration in Webex.',
        parameters: {
          type: 'object',
          properties: {
            roomId: {
              type: 'string',
              description: 'The ID of the room where the folder will be linked.'
            },
            contentUrl: {
              type: 'string',
              description: 'The URL of the content associated with the folder.'
            },
            displayName: {
              type: 'string',
              description: 'The display name for the folder.'
            },
            driveId: {
              type: 'string',
              description: 'The ID of the drive where the folder is located.'
            },
            itemId: {
              type: 'string',
              description: 'The ID of the item (folder) to be linked.'
            },
            defaultFolder: {
              type: 'boolean',
              description: 'Whether this folder is the default folder.'
            }
          },
          required: ['roomId', 'contentUrl', 'displayName', 'driveId', 'itemId']
        }
      }
    }
  • lib/tools.js:7-16 (registration)
    The discoverTools function dynamically imports all tool modules listed in toolPaths and extracts/registers their apiTool objects for use in the MCP server.
    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);
    }
  • tools/paths.js:41-41 (registration)
    The specific path to this tool's file is included in the toolPaths array, enabling its discovery and registration by discoverTools().
    'webex-public-workspace/webex-messaging/create-an-ecm-folder-configuration.js',
Behavior2/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. It states 'Create' which implies a write operation, but doesn't mention permissions required, whether it's idempotent, error handling, or what happens on success (e.g., returns a folder ID). This leaves significant gaps for an agent to understand the tool's 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. Every word contributes directly to stating the tool's purpose.

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 complexity of a creation tool with 6 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns, error conditions, or behavioral nuances like whether 'defaultFolder' being optional affects the outcome. This leaves the agent with insufficient context for reliable use.

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 input schema fully documents all 6 parameters with descriptions. The description adds no additional parameter semantics beyond implying a folder is created, which aligns with the schema. 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 ('Create') and resource ('ECM folder configuration in Webex'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'list_ecm_folder' or 'update_ecm_linked_folder' beyond the basic verb, missing explicit comparison.

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 'update_ecm_linked_folder' or 'unlink_ecm_linked_folder'. The description lacks context about prerequisites, such as needing an existing room or drive, or when creation is appropriate over other operations.

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