Skip to main content
Glama

Set or remove my photo

profile_avatar_set

Sets or removes your own profile photo. Give an https image_url or a small image_base64 (PNG, JPEG or WebP, at least 120 px), or clear:true to remove it. The server re-encodes the picture to a square WebP and removes its metadata. The photo link is public. Call without confirm first for a preview with the image size.

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_avatar_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
clearNoRemove the current photo instead of uploading.
confirmNoSet true only on the second call, after the user approved the preview.
image_urlNohttps URL of a PNG, JPEG or WebP image (max 5 MB, 120-6000 px). Fetched by the server.
image_base64NoSmall image as base64 (about 180 KB at most); use image_url for anything larger.
preview_tokenNoThe preview_token returned by the first call (same input).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well past the annotations: discloses server-side re-encoding to square WebP, metadata stripping, that the resulting photo link is public (a real privacy consequence given openWorldHint=true), and the preview-then-confirm protocol. This is exactly the context annotations cannot convey.

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 short sentences, each carrying distinct information: purpose, input options, server behavior plus privacy, and the preview workflow. No repetition of the title and no 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?

For a 5-parameter mutation tool with no output schema, the description covers the input choices, the mutation's side effects, the visibility of the result, and the confirm-flow outcome (preview with image size). Nothing an agent needs to call it correctly 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 meaning the schema does not spell out: the 120 px minimum, the size tradeoff that selects base64 over url, and the ordering constraint that confirm applies only to the second call with the same input.

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 pair and resource ('Sets or removes your own profile photo'), and 'your own' scopes it away from sibling team_avatar_set. An agent can immediately tell what it does without opening the schema.

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?

Gives concrete operating guidance: provide image_url, image_base64, or clear:true, and 'Call without confirm first for a preview with the image size,' which defines the required two-step sequence. It does not explicitly contrast with team_avatar_set, but 'your own' supplies the implied boundary.

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