Skip to main content
Glama

Set profile portrait

well_update_profile_portrait
Destructive

Make one portrait of the person's newest portrait round their profile photo, in place of the one they have.

Call it only with the round_id and the media_id of a portrait Well composed for the person who asks, as the portrait message named them. Never guess an id. The portrait replaces the current profile photo, and the old photo is deleted. Only the newest round can be set, and only once: a refusal_reason says why nothing was set; say it in one line, in the language of the conversation.

When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.

Input Schema

NameRequiredDescriptionDefault
media_idYesThe id of the one portrait of that round to set.
round_idYesThe id of the portrait round, as the portrait message named it.
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
idempotency_keyNoOptional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
errorNo
groundNoThe ground of the portrait set.
successYes
refusal_reasonNoWhy nothing was set.
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
profile_media_idNoThe media of the new profile photo.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

The description substantiates the destructive annotation by stating that the current profile photo is deleted, adds a one-shot constraint beyond the annotations, and explains the failure mode (a refusal_reason explaining why nothing was set, to be relayed in one line). This is genuinely useful context an agent could not derive from the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the required-id rule are front-loaded, and every paragraph carries information. Some prose is ornate ('round their profile photo, in place of the one they have'), and the workspace paragraph is slightly dense, but nothing is filler.

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?

An output schema exists, so return values need no explanation; the description still covers the destructive side effect, the retry/one-shot limit, the refusal path, and the workspace selection rule. Nothing an agent needs in order to invoke this safely is missing.

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 baseline is 3, but the description adds operational meaning: the ids must come from the portrait message ('as the portrait message named them') and workspace_id is required only when the token authorizes several workspaces, in which case a preliminary workspace call is unnecessary. That conditional routing nuance is not obviously derivable from the schema alone.

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 names a concrete verb and resource: setting one portrait of the newest portrait round as the person's profile photo, replacing the existing one. It is specific enough to distinguish this from the update/list tools in the sibling set, though the phrasing 'Make one portrait ... round their profile photo' is slightly tangled and takes a re-read.

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?

It gives explicit preconditions and exclusions: 'Never guess an id', 'Only the newest round can be set, and only once', and it explains when a workspace_id is needed versus when the call can be made directly. No alternative sibling is named, but none is obviously interchangeable with this one, so the gap is minor.

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