Skip to main content
Glama

update_my_professional

Update the coach's own professional info — specialties, certifications, years of experience, bio, languages, business type, social links (Instagram, Facebook, TikTok, YouTube, website) and media links (confirm-gated). Sends the full object; read get_my_profile first if only changing one field. Leave socialLinks / mediaLinks out to keep the saved ones; pass the whole list to change them ([] removes all).

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": {
      "specialties": "<specialties>",
      "certifications": "<certifications>",
      "yearsOfExperience": "<yearsOfExperience>",
      "businessType": "<businessType>",
      "languages": "<languages>",
      "profilePhoto": "<profilePhoto>",
      "gallery": "<gallery>",
      "certificateFiles": "<certificateFiles>"
    },
    "name": "update_my_professional"
  }
}

Input Schema

NameRequiredDescriptionDefault
bioNo
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
galleryYes
languagesYes
mediaLinksNo
socialLinksNo
specialtiesYes
businessTypeYes
profilePhotoYes
certificationsYes
certificateFilesYes
yearsOfExperienceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / mediaLinks
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "link": {
      +        "format": "uri",
      +        "type": "string"
      +      },
      +      "name": {
      +        "minLength": 1,
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "link"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
    • addedInput schema / properties / socialLinks
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "link": {
      +        "format": "uri",
      +        "type": "string"
      +      },
      +      "name": {
      +        "description": "e.g. instagram, facebook, tiktok, youtube, website",
      +        "minLength": 1,
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "link"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior1/5

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

The description contains useful behavioral detail, including that the tool sends the full object and that passing [] removes all social/media links. However, this directly contradicts the annotation destructiveHint=false: clearing all saved links is a destructive update. The confirm gate does not resolve the contradiction because the annotation makes an unconditional safety claim.

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?

The description is dense and front-loaded, starting with the core action and then covering operational caveats. Parenthetical field lists are efficient, and there is no filler or repetition.

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 12-parameter mutation with no output schema and very low schema coverage, the description covers the critical workflow: read-before-update guidance, full-object behavior, confirm-gated execution, and link retention/removal semantics. It falls short by not mentioning the required profilePhoto, gallery, and certificateFiles fields, which an agent still has to infer from the schema.

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?

With only 8% schema description coverage across 12 parameters, the description must compensate, and it does explain the important socialLinks/mediaLinks omission-vs-replacement semantics plus the full-object requirement. It still omits required parameters profilePhoto, gallery, and certificateFiles, and confirm is only documented in the schema, so coverage remains incomplete.

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?

The description states a specific verb and resource — updating the coach's own professional information — and enumerates the covered fields (specialties, certifications, experience, bio, languages, business type, links). It clearly distinguishes this from the sibling get_my_profile by explaining that get_my_profile should be read first when only one field is changing.

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

Usage Guidelines5/5

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

It gives explicit usage guidance: read get_my_profile first if only changing one field, and omit socialLinks/mediaLinks to preserve saved values or pass the entire list to replace them. The full-object semantics and list replacement behavior are spelled out, leaving little to inference.

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.