Skip to main content
Glama
Files-com

Files.com MCP Server

Official
by Files-com

Create User

Create_User

Provision a new user on Files.com, setting username, email, password, group memberships, authentication method, and home folder paths.

Instructions

Create User

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameNoUser's username
emailNoUser's email.
group_idsNoA list of group ids to associate this user with. Comma delimited.
passwordNoUser password.
authentication_methodNoHow is this user authenticated?
nameNoUser's full name
companyNoUser's company
notesNoAny internal notes on the user
require_password_changeNoIs a password change required upon next user login?
user_rootNoRoot folder for FTP (and optionally SFTP if the appropriate site-wide setting is set). Note that this is not used for API, Desktop, or Web interface.
user_homeNoHome folder for FTP/SFTP. Note that this is not used for API, Desktop, or Web interface.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

The annotations already indicate readOnlyHint=false (write operation) and destructiveHint=false (not destructive). The description adds no behavioral context such as side effects, authentication requirements, or return value details.

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?

The description is only two words, which is under-specification rather than conciseness. It gives no structural guidance or front-loaded critical information.

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?

With 11 optional parameters and an output schema, the description should at least confirm that it creates a new user account. It lacks essential context for an AI agent to invoke the tool 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?

Schema coverage is 100%, so the baseline is 3. The description does not add any meaning beyond the schema, but the schema itself provides adequate descriptions for all 11 parameters.

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

Purpose1/5

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

Tautological: description restates name/title.

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 usage guidelines are provided. The description fails to indicate when to use this tool versus alternatives like Create_Group or Update_User, nor does it mention any prerequisites or exclusions.

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/Files-com/files-mcp'

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