Skip to main content
Glama

Team: update my public profile

team_profile_update_self
Idempotent

Updates your own Our Team profile (names, headline, bio, skills, experience, education, projects, links), records steps you skipped, and sets which contact details are published. Only your own record and only these public fields; it cannot change roles, access, email or other people. Returns the new completion percent and the next question. Call without confirm first for a preview.

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

Input Schema

NameRequiredDescriptionDefault
skipNoSteps the member chose to skip. A skipped step is not counted as done.
namesNoPer-language spelling of the name, approved by the member, e.g. {ar:{first_name:'...'}}. Ask how they spell it; never translate meaning.
localeNoLanguage slot the names are written to.en
unskipNoSteps to ask again.
confirmNoSet true only on the second call, after the user approved the preview.
profileNoOnly the fields you send change. Lists replace the whole list.
last_nameNo
first_nameNoYour first name in `locale`.
visibilityNoPublish contact details on the public page. Only true when the member explicitly agreed; default is hidden.
preview_tokenNoThe preview_token returned by the first call (same input).
fill_missing_onlyNoUse when saving translations: only EMPTY language slots are written; existing text is never overwritten (lists must keep their item count).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, so the safety profile is covered. The description adds genuinely new behavior: a preview/confirm two-step, that skipped steps are recorded and not counted as done, that it returns a completion percent plus the next question, and that contact details are published only on explicit agreement. It does not discuss failure modes or what a preview response contains.

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-loaded with the action and scope, then the constraints, then the call sequence. Dense but every clause carries information an agent needs; nothing is redundant with the title.

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 an 11-parameter nested mutation with no output schema, the description supplies the return shape (completion percent and next question) and the two-call protocol, which is the critical missing piece. Minor gaps remain around preview_token reuse and list-replacement behavior, though the latter is covered in 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?

Schema coverage is 91%, so the baseline is 3, but the description adds meaning the schema does not: skip versus unskip as a record/ask-again pair, and visibility as an explicit-consent publishing switch. It does not explain preview_token or fill_missing_only, which remain schema-only.

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 (updates your own Our Team profile) and enumerates the field families it covers. It also draws a hard boundary — only your own record, only public fields, cannot change roles, access, email or other people — which lets an agent separate it from profile_update or company_update without opening a 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 an explicit operating procedure: call without confirm first for a preview, then confirm. It also states the negative scope (not roles, access, email, other people), which implicitly routes those needs elsewhere. It stops short of naming a specific sibling for the excluded cases.

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