Skip to main content
Glama

AIApply

Send a reviewed AIApply application to the employer

submit_application
DestructiveIdempotent

Use this only when the connected user has asked for one specific job from their review queue to be applied for, identified by the job_id from list_review_jobs. Approving it spends one application credit and cannot be undone: AIApply writes the application and sends it to the employer. Show the user the job from list_review_jobs and get their explicit go-ahead first, then call again with confirmed=true. AIApply has not written the application yet at this point, so there is nothing to preview. Approving the same job twice is refused rather than repeated. Needs an AIApply account: if the user has not signed in, calling it asks them to sign in or create one. It also needs a permission the user grants; if it was not granted, calling it asks the user to allow it.

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": {
      "job_id": "<job_id>",
      "confirmed": "<confirmed>"
    },
    "name": "submit_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job_id from list_review_jobs.
confirmedYesTrue only after the user has been shown this application and agreed to send it.

Output Schema

NameRequiredDescriptionDefault
errorNoTrue when the send could not be completed.
foundNoFalse when no such application belongs to the account.
reasonNoWhy nothing was sent, when nothing was.
appliedNoTrue only when the application was sent.
messageYes
user_messageNoShow this to the user rather than message.
dashboard_urlNoThe AIApply dashboard, where the user manages Auto Apply.
previous_statusNoPresent only on a successful send: the status it was in before.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructive, non-read-only, open-world, idempotent; the description adds real substance beyond them — it spends one application credit, the send cannot be undone, duplicates are refused rather than repeated, and both an account and a granted permission are needed with the tool itself prompting sign-in or consent. The main gap is that it doesn't say what the tool returns on success (an output schema exists, so that's a minor omission).

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-loaded with the 'only when' condition, then irreversibility and credit cost, then the confirmation workflow and edge cases. It's a dense single paragraph but every sentence carries a distinct constraint; the auth sentences are the most verbose part and could be tightened.

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 destructive, credit-spending, open-world action, the description covers cost, irreversibility, confirmation protocol, duplicate handling, and the two auth preconditions, and an output schema exists so return values needn't be explained. Nothing an agent needs to call this safely 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 baseline is 3; the description still adds the operational meaning of the parameters by tying job_id to list_review_jobs and by specifying that confirmed=true comes only after the user has been shown the job and agreed — a sequencing constraint the schema states more tersely.

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 — AIApply writes the application and sends it to the employer — and scopes it to a single job from the review queue identified by job_id from list_review_jobs. The line 'AIApply has not written the application yet at this point, so there is nothing to preview' implicitly separates it from the preview flow. An agent can tell what this does and where the input comes from without opening 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 Guidelines5/5

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

Explicit gating: 'Use this only when the connected user has asked for one specific job from their review queue to be applied for.' It also states the required two-step sequence — show the job, get explicit go-ahead, then call with confirmed=true — and that a duplicate approval is refused. That is when-to-use, prerequisite, and negative case all in one paragraph.

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