Galatic.ai

Update profile

update_profile

Update the signed-in user's public creator profile and return it as { profile }. Only the fields you pass change; socialLinks is replaced as a whole, not merged, and a call with no fields is refused (400). isPublic false hides the profile page from other users and from profile search and suggestions (default true). Use get_profile first to see the current values. The change is visible to other users when the profile is public.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "update_profile"
  }
}

Input Schema

Name	Required	Description
`bio`	No
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`website`	No
`coverUrl`	No	Cover image URL.
`isPublic`	No	false hides the profile from other users and from search.
`location`	No
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`displayName`	No	Name shown on the profile.
`socialLinks`	No	Replaces the whole socialLinks object.
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 26, 2026
- addedInput schema / properties / coverUrl / description
```
Added value: +"Cover image URL."
```
- addedInput schema / properties / displayName / description
```
Added value: +"Name shown on the profile."
```
- addedInput schema / properties / isPublic / description
```
Added value: +"false hides the profile from other users and from search."
```
- addedInput schema / properties / socialLinks / description
```
Added value: +"Replaces the whole socialLinks object."
```
First observedOct 24, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations (which only say it is a non-read-only, non-destructive, non-idempotent write): it discloses partial-update semantics, whole-object replacement of socialLinks, a 400 on empty payloads, the isPublic default of true, and the concrete consequence of hiding (no profile page, no search or suggestions). This is exactly the kind of contract detail an agent needs before mutating a public-facing 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?

Front-loads the action and return value, then layers semantics, error behavior, and visibility consequences in short clauses. No filler and nothing repeated from the schema.

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?

Return value ({ profile }), default values, error cases, and visibility impact are all covered despite there being no output schema. What is left out is minor: permission/ownership constraints are only implied by "signed-in user's" profile and the analytics params are left entirely to the schema.

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?

Adds real meaning for the highest-risk params: socialLinks is replaced not merged, and isPublic false has a specific visibility effect with a stated default of true. Schema coverage is 70% and the simple string fields (bio, website, location) carry no extra detail from either source, so it stops short of full compensation.

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?

States a specific verb and resource ("Update the signed-in user's public creator profile") plus the return shape. It is unmistakable against the sibling get_profile, which it explicitly routes to for reading current values.

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

Usage Guidelines4/5

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

Explicitly names get_profile as the prerequisite step and warns that a no-field call is refused, which prevents a common failure. It does not state when a caller should avoid this tool entirely, but for a self-scoped update the alternatives are few.

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

All Galatic.ai tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.