Skip to main content
Glama

Cloud Profile Manage Tool

profile_manage

Manage your profile, password, 2FA, and linked OAuth accounts: read or update profile, change password, check 2FA status, and unlink social providers.

Instructions

Caller's own profile and account settings (name, email, password, 2FA, OAuth links). Operates on the authenticated user — there is no user_id parameter; super-admins managing other users use admin_manage instead. All actions are rate-limited per user (60/min) and audit-logged.

When to use: agent or assistant needs to read/update the current user's profile, list linked OAuth providers, or unlink a social provider. Do NOT use to create accounts (that's a self-service signup flow only).

Actions:

  • get (read) — returns profile object: name, email, locale, timezone, current_team_id, last_login_at, email_verified_at.

  • update (write) — optional fields: name, email, locale, timezone. Email change re-issues the verification mail and clears email_verified_at until confirmed.

  • password_update (DESTRUCTIVE; rotates session) — current_password, password, password_confirmation. Verifies current password then bcrypts the new one; revokes all OTHER active sessions of this user.

  • 2fa_status (read) — returns { enabled: bool, recovery_codes_remaining: int }.

  • connected_accounts (read) — list of linked OAuth provider records (provider, provider_user_id, linked_at).

  • social_list (read) — duplicate of connected_accounts kept for backward client compatibility.

  • social_unlink (DESTRUCTIVE) — provider. Removes the OAuth link; rejected with 422 if it would leave the user with no remaining auth method.

Errors: 401 unauthenticated; 403 if Sanctum token lacks team:{id} ability; 422 for validation; 429 on rate limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: get, update, password_update, 2fa_status, connected_accounts, social_list, social_unlink
deadline_msNoOptional: max wall-clock time (ms) the tool may spend. If exceeded during the call, returns a DEADLINE_EXCEEDED error. Minimum 100 ms. Leave unset for no deadline.
nameNo
emailNo
current_passwordNo
passwordNo
password_confirmationNo
providerNoThe social provider to disconnect.
Behavior5/5

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

Annotations are empty, so description bears full burden. Discloses side effects for each action: email update re-issues verification and clears email_verified_at, password_update is destructive and revokes sessions, social_unlink may be rejected if no remaining auth method. Also mentions rate limits and audit logging.

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?

Well-structured: overview, usage guidance, then action list with behaviors. Every sentence adds value. No redundancy.

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

Completeness5/5

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

Given complexity (multiple actions, side effects, no output schema), description covers all actions, their parameters, side effects, and error cases (401, 403, 422, 429). Missing explicit return format but described inline (e.g., profile object fields, 2fa_status returns {enabled, recovery_codes_remaining}). Highly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 38% (low), but description adds semantics for action-specific parameters (e.g., update fields are optional, password_update requires current_password/password/password_confirmation, provider enum values). Does not describe deadline_ms but it is optional. Compensates well for low coverage.

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

Purpose5/5

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

Clearly states it operates on the caller's own profile/account settings, lists supported actions (get, update, password_update, etc.), and distinguishes from sibling tool admin_manage. Specific verbs and resource identified.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use instructions ('agent or assistant needs to read/update the current user's profile...'), excludes account creation (self-service signup), and references admin_manage as an alternative for managing other users.

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/escapeboy/agent-fleet-o'

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