remoet

Update Profile

update_profile

Idempotent

Update the user's Remoet profile core and/or their visibility. Only provide the fields you want to change. Omitted fields are left as-is; pass null to clear a field. If the source data (CV, website, etc.) is missing a field, ask the user rather than guessing. Never copy placeholder text like "lorem ipsum".

VISIBILITY: pass visibility to control who can see the profile in company candidate lists: NONE (hidden), STARRED (only companies the user has starred, the recommended two-way match), or ALL (every company). Explain the trade-off before changing it.

SUMMARY WRITING GUIDE: the summary is the most important field, the first thing companies read. Pattern: [Role] with [X years] experience in [core tech stack]. [One differentiator or achievement]. Example: "Senior Full-Stack Developer with 8 years of experience in React, Node.js, and AWS. Built and scaled a SaaS platform serving 200K users." Under 500 characters. Avoid generic fluff like "passionate developer". Be specific and quantifiable.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	Your personal website URL
`name`	No	Your full name
`slug`	No	Your public profile URL slug (must be unique)
`email`	No	Update your email address
`phone`	No	Your phone number
`summary`	No	A brief professional summary or bio
`location`	No	Your location
`avatarUrl`	No	Your avatar/photo URL
`githubUrl`	No	Your GitHub profile URL
`twitterUrl`	No	Your Twitter/X profile URL
`visibility`	No	Who can see the profile in company candidate lists: NONE (hidden), STARRED (only companies the user has starred, recommended), ALL (every company). Explain the trade-off before changing.
`youtubeUrl`	No	Your YouTube channel URL
`facebookUrl`	No	Your Facebook profile URL
`linkedinUrl`	No	Your LinkedIn profile URL

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 1, 2026

removedInput schema / properties / email / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / email / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedInput schema / properties / slug / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / slug / type

Added value: +[
+  "string",
+  "null"
+]

Changed4 schema fields changedOct 1, 2026

addedInput schema / properties / email / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / email / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

addedInput schema / properties / slug / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / slug / type

Removed value: -[
-  "string",
-  "null"
-]

Changed4 schema fields changedOct 1, 2026

removedInput schema / properties / email / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / email / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedInput schema / properties / slug / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / slug / type

Added value: +[
+  "string",
+  "null"
+]

First observedSep 16, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, openWorld=false, so safety profile is covered. The description adds valuable behavior beyond that: partial-update semantics (omitted vs null), and the semantic meaning of each visibility mode with a recommendation. It does not mention auth requirements, but this is a strong contribution.

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?

Front-loads the key update rule, then uses clear headers (VISIBILITY, SUMMARY WRITING GUIDE) to organize supplementary guidance. It is longer than most definitions but the visibility explanation and summary guide each earn their place rather than being 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 14-param, all-optional mutation tool with no output schema, the description covers everything an agent needs: partial-update behavior, field-clearing, the one enum's options, and guidance for the highest-value field. Nothing material 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. The description exceeds that by adding meaningful semantics for two parameters the schema only labels: it defines what each visibility enum value does and the trade-off, and provides a structured writing pattern, length limit, and example for the summary field.

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: 'Update the user's Remoet profile core and/or their visibility.' It clearly scopes the tool to core fields plus visibility, distinguishing it from sibling tools like save_work_experience, save_project, and save_education that handle separate profile items.

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?

Gives explicit operating rules: 'Only provide the fields you want to change. Omitted fields are left as-is; pass null to clear a field.' It also says to ask the user when source data is missing a field rather than guessing, and to explain the visibility trade-off before changing it. These are concrete when/when-not instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All remoet tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?