Skip to main content
Glama

Update my profile

profile_update
Idempotent

Changes your own profile fields: first_name, last_name, phone, about_me and company. Send only the fields to change; the others stay as they are, and null or an empty text clears phone, about_me or company. The name is saved for the chosen locale only; other languages are kept. The email address cannot be changed here (website only). Call without confirm first for a before/after preview, then again with confirm and the preview_token.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "profile_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneNoPhone with country code, digits 7-15. null or empty clears it.
localeNoLanguage slot for the names. Default en.
companyNoCompany name. null or empty clears it.
confirmNoSet true only on the second call, after the user approved the preview.
about_meNoPlain text about you, up to 600 characters, up to 6 lines. null or empty clears it.
last_nameNoLast name in the chosen locale. Empty is allowed.
first_nameNoFirst name in the chosen locale.
preview_tokenNoThe preview_token returned by the first call (same input).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark this as a non-read-only, idempotent, non-destructive write, and the description adds substantially beyond them: partial-update semantics (unsent fields are preserved), how to clear optional values via null/empty, per-locale name storage, and the mandatory two-step preview/confirm sequence. This is exactly the context an agent needs before mutating a profile.

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?

Four compact sentences with no filler: what changes, how partial updates and clearing work, the locale caveat, the excluded field, and the two-step call flow. The most operationally risky information (preview then confirm) is placed last as the call-to-action rather than buried.

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

Completeness4/5

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

With eight optional parameters, no output schema, and an unusual two-call protocol, the description covers nearly everything needed to invoke it correctly. The one gap is the preview_token lifecycle — no expiry, reuse, or mismatch behavior is stated, which matters if the agent delays the confirming call.

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 coverage is 100%, so the base expectation is 3; the description rises above that by explaining cross-field behavior the schema cannot express, notably that names are saved only for the chosen locale and other languages are kept, and by summarizing the are-these-cleared semantics in one place.

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 opens with a specific verb and resource ('Changes your own profile fields') and enumerates the mutable fields, so the operation is unmistakable. The word 'own' implicitly separates it from team-oriented siblings, but listing 'company' among personal fields blurs the line with company_update, and no sibling is named explicitly.

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?

It gives explicit procedural guidance: call first without confirm for a before/after preview, then again with confirm plus the preview_token. It also states an exclusion ('the email address cannot be changed here (website only)'), which sends the agent elsewhere for that case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources