Skip to main content
Glama

AceRound AI Interview Copilot

record_submitted_job

Record a job the user already applied to elsewhere (company and title entered by hand); it is saved as submitted and tracked, without using Auto Apply credits. For jobs in the job library use mark_campus_job_submitted. (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": {
      "company": "<company>",
      "jobTitle": "<jobTitle>"
    },
    "name": "record_submitted_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
citiesNoWork locations (optional)
jobUrlNoJob link (optional)
companyYesCompany name
jobTitleYesJob title

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare it is a non-destructive write, and the description adds genuinely new context: the record is 'saved as submitted and tracked', it consumes no Auto Apply credits, and it requires sign-in with the job_applications:write scope. That is meaningful disclosure beyond the annotations; what is missing is duplicate-detection behavior and any note on what the caller gets back.

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?

Two sentences, front-loaded with the primary action and effect, followed by the sibling routing rule, then a compact parenthetical auth note. Every clause carries distinct information and nothing is repeated from the title or schema.

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 four-parameter, non-destructive write with no output schema, the description covers purpose, side effect, cost, auth requirement, and the alternative tool. It stops short of describing duplicate handling or confirmation of what is created, which would make it fully self-sufficient.

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%, so all four parameters (company, jobTitle, cities, jobUrl) are already documented in the schema. The description confirms company and title are hand-entered but adds no format, length, or validation semantics for cities or jobUrl beyond what the schema states, so the baseline 3 applies.

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 ('Record a job the user already applied to elsewhere') and pins the scope with parenthetical detail on how the inputs are supplied ('company and title entered by hand'). It also distinguishes itself from the sibling mark_campus_job_submitted, so an agent can route between the two 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 Guidelines5/5

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

Gives an explicit when-to-use condition (job already applied to elsewhere, entered manually) and an explicit when-not with the named alternative ('For jobs in the job library use mark_campus_job_submitted'). The only unstated case is duplicate re-recording, which is a minor omission against otherwise complete routing guidance.

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