JobGPT

update_profile

Update your user profile fields

Input Schema

TableJSON Schema

Name	Required	Description
`gender`	No	Gender
`skills`	No	List of skills (e.g., ["Python", "JavaScript", "AWS"])
`headline`	No	Professional headline (e.g., "Senior Software Engineer at Google")
`lastName`	No	Your last name
`location`	No	Your location (e.g., "San Francisco, CA")
`ethnicity`	No	Ethnicity
`firstName`	No	Your first name
`experience`	No	Years of experience
`phoneNumber`	No	Phone number without country code (e.g., "4084586677")
`phoneCountryIso`	No	ISO country code for the phone number (e.g., "US", "IN")
`noticePeriodDays`	No	Notice period in days (0-180)
`openToRelocation`	No	Whether you are open to relocating for a job
`phoneCountryCode`	No	Phone country dial code with + prefix (e.g., "+1" for US, "+91" for India)
`workPermitLocations`	No	Countries where you have work authorization, as ISO country codes (e.g., ["US", "CA", "GB"])
`immigrationSponsorshipRequired`	No	Whether you require immigration/visa sponsorship (e.g., H1B)

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedApr 8, 2026

addedInput schema / properties / ethnicity

Added value: +{
+  "description": "Ethnicity",
+  "type": "string"
+}

addedInput schema / properties / firstName

Added value: +{
+  "description": "Your first name",
+  "type": "string"
+}

removedInput schema / properties / fullName

Removed value: -{
-  "description": "Your full name",
-  "type": "string"
-}

addedInput schema / properties / gender

Added value: +{
+  "description": "Gender",
+  "enum": [
+    "male",
+    "female"
+  ],
+  "type": "string"
+}

addedInput schema / properties / immigrationSponsorshipRequired

Added value: +{
+  "description": "Whether you require immigration/visa sponsorship (e.g., H1B)",
+  "type": "boolean"
+}

addedInput schema / properties / lastName

Added value: +{
+  "description": "Your last name",
+  "type": "string"
+}

addedInput schema / properties / noticePeriodDays

Added value: +{
+  "description": "Notice period in days (0-180)",
+  "type": "number"
+}

addedInput schema / properties / openToRelocation

Added value: +{
+  "description": "Whether you are open to relocating for a job",
+  "type": "boolean"
+}

addedInput schema / properties / phoneCountryCode

Added value: +{
+  "description": "Phone country dial code with + prefix (e.g., \"+1\" for US, \"+91\" for India)",
+  "type": "string"
+}

addedInput schema / properties / phoneCountryIso

Added value: +{
+  "description": "ISO country code for the phone number (e.g., \"US\", \"IN\")",
+  "type": "string"
+}

addedInput schema / properties / phoneNumber

Added value: +{
+  "description": "Phone number without country code (e.g., \"4084586677\")",
+  "type": "string"
+}

addedInput schema / properties / workPermitLocations

Added value: +{
+  "description": "Countries where you have work authorization, as ISO country codes (e.g., [\"US\", \"CA\", \"GB\"])",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

First observedMar 23, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only repeats the action ('Update your user profile fields') without explaining whether it's a partial update, whether it modifies the authenticated user's profile exclusively, or any side effects. This is inadequate for a mutation tool.

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?

The description is a single concise sentence that is front-loaded and free of fluff. It is appropriately short for a tool whose parameter details are fully documented in the schema, though it borders on under-specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 15 parameters and no output schema, the description is incomplete. It fails to mention that all parameters are optional, that only provided fields will be updated, or what the response contains. This is a significant gap for a tool of this complexity, making it much less useful than it could be.

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%, meaning all 15 parameters have detailed descriptions in the input schema. The tool description itself adds no parameter semantics, but since the schema already covers them, the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Update') and resource ('user profile fields'). It distinguishes from siblings like get_profile (read-only) and update_salary (salary-specific). However, it lacks detail on which fields are included, leaving that to 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 Guidelines2/5

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

There is no explicit guidance on when to use this tool or when to prefer alternatives. It does not mention exclusive conditions, prerequisites, or a note like 'Use update_salary for salary changes.' The usage context is only implicitly derived from the tool's name.

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

All JobGPT tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?