Skip to main content
Glama

AceRound AI Interview Copilot

update_job_apply_profile

Update standard fields in the user's Auto Apply profile: only the keys passed change; an empty string or array clears a field. Keys are listed by get_job_apply_profile. Replies with the values as read back. (Requires the user's sign-in with scope job_applications:write.)

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": {
      "patch": "<patch>"
    },
    "name": "update_job_apply_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchYesFields to change: standard field key to a string or an array of strings (one item per entry for repeated sections)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: patch (not replace) semantics, the clearing behavior for empty values, the required sign-in scope job_applications:write, and the fact that the response echoes the values as read back. These are exactly the behavioral facts an agent needs before calling 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the action and scope, followed by mutation semantics, return behavior, and auth. No redundant restatement of the tool name or schema.

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 single nested-object mutation parameter with no output schema, the description covers what changes, how to clear, where keys come from, the auth requirement, and what comes back. Nothing essential to correct invocation 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, but the description earns an extra point by explaining semantics the schema does not encode: partial-update behavior and how empty string/array is interpreted as a clear. It still leaves value formats (e.g., date format for birthDate, ranges) to inference.

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?

Opens with a specific verb and resource ("Update standard fields in the user's Auto Apply profile") and pins down the scope as standard fields only. It points to get_job_apply_profile for the key vocabulary, which separates it from the read sibling, though it does not explicitly contrast with delete_job_apply_profile_field.

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 clear operative guidance: only the keys passed are changed, and an empty string or array clears a field. Key discovery is routed to get_job_apply_profile. It stops short of stating when to prefer this over delete_job_apply_profile_field or the resume-extraction sibling.

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