Skip to main content
Glama
Files-com

Files.com MCP Server

Official
by Files-com

Update User

Update_User
Destructive

Modify user account details including email, password, group memberships, and folder assignments in Files.com.

Instructions

Update User

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoUser ID.
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.
usernameNoUser's username

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Annotations already indicate destructiveHint=true, but the description adds no additional behavioral context such as required permissions, whether changes are immediate, or edge cases. With annotations present, the description still fails to provide meaningful transparency.

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?

At two words, it is excessively brief and under-specified. It lacks front-loaded information and fails to earn its place by conveying necessary usage details.

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

Completeness1/5

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

Despite 12 parameters and a destructive mutation, the description provides no guidance on effects, required fields, or complementing output schema. It is completely inadequate for an agent to safely invoke the tool.

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 baseline is 3. The description does not add any semantics beyond what the schema already provides, but does not detract either.

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 guidance is provided on when to use this tool versus alternatives (e.g., Create_User, Delete_User). There is no mention of prerequisites, exclusions, or context.

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