Skip to main content
Glama

AceRound AI Interview Copilot

mark_campus_job_submitted

Mark a job from the job library as already applied to elsewhere: creates the application if needed and records it as submitted; already-submitted ones keep their date. Does not use Auto Apply credits. (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": {
      "campusJobId": "<campusJobId>"
    },
    "name": "mark_campus_job_submitted"
  }
}

Input Schema

NameRequiredDescriptionDefault
campusJobIdYesJob id, from search_campus_jobs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the side effect of creating an application if none exists, the idempotent behavior (already-submitted entries keep their date), the credit cost (none), and the required auth scope job_applications:write. These are exactly the facts an agent needs before invoking a mutation.

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?

One dense sentence with a parenthetical for the auth requirement, front-loaded with the core action and side effect. Efficient, though the clause stacking ('creates the application if needed and records it as submitted; already-submitted ones keep their date') is slightly heavy.

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 one-parameter mutation with no output schema, the definition covers side effects, idempotency, cost, and permissions. The only gap is that the return value (e.g., whether the created application or its id is returned) is unstated.

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% and the single parameter campusJobId is already documented as coming from search_campus_jobs, so the schema carries the burden. The description adds no further meaning about the id format or validation, which is acceptable at baseline.

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?

Names a specific verb and resource ('Mark a job from the job library as already applied') and adds the key disambiguation that this acts on library jobs applied 'elsewhere', which sets it apart from the application-centric siblings. It stops short of naming a concrete alternative tool, so an agent must infer the routing from the phrase 'job library'.

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?

The scenario is clear: use this when the user has already applied to a library job externally, and the note that it 'does not use Auto Apply credits' implies it is not the automated-apply path. There is no explicit 'use X instead when...' routing, which keeps it below a 5.

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