Skip to main content
Glama

Team: change my profile photo

team_avatar_set

Sets or removes your own profile photo (the picture in your Our Team header). Give an https image_url or a small image_base64; PNG, JPEG or WebP. Only your own record. 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": "team_avatar_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
clearNoRemove the current image instead of uploading (the page falls back to its default).
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.2/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false, idempotent=false) the description discloses the two-phase preview/confirm protocol, the accepted formats, that the server fetches the URL, and that clearing falls back to the page default. It stops short of stating what happens if preview_token is stale or a URL fetch fails, so the error behaviour is undocumented.

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?

Two sentences, each doing distinct work: sentence one defines the operation, scope and formats; sentence two defines the safe call sequence. Nothing is redundant and the ownership constraint is placed early, before the procedural detail.

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?

For a 5-parameter mutation with no output schema and full schema coverage, the description supplies the context an agent actually needs: ownership boundary, format/size constraints, and the preview-before-confirm workflow. Only failure modes and preview_token lifetime are left implicit, a minor gap given the schema does the rest.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter is already documented in the schema, including the preview/confirm two-call rule and the image_base64 size caveat. The description's parameter-relevant content largely restates those facts ('Give an https image_url or a small image_base64', 'Call without confirm first'), so it earns the baseline rather than exceeding it.

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 parenthetically pins it to the visible artifact ('the picture in your Our Team header'). The ownership scope ('Only your own record') further separates it from team-wide image tools in the sibling list.

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 an explicit operating procedure: 'Call without confirm first for a preview with the image size', which tells the agent the correct call sequence rather than leaving it to inference. It does not name the closest sibling alternatives (e.g. profile_avatar_set or team_about_image_set) or say when one should be chosen over this one.

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