Skip to main content
Glama

AceRound AI Interview Copilot

send_job_apply_instruction

Destructive

Pass one message to the apply AI on the user's computer, exactly as if the user typed it in the app's chat, e.g. "apply to everything on my list" or "pick 10 backend new-grad roles that match my resume". By default it goes to the persistent Skills conversation (opened on first use); pass taskId to send it to a specific conversation. If that conversation is running, the message does not interrupt it: it is handed over with the next step or queued until the turn ends. When the apply AI applies because of it, each application uses 1 Auto Apply credit once it is filled up to the submit step or submitted (once per application; nothing while unlimited is active). Replies with where the app put it (started / handed over with the next step / queued) and the conversation id; then use get_job_apply_client_status for progress and the AI's replies. Requires the AceRound Auto Apply desktop app on the user’s computer to be signed in and open (running in the background after closing the window also works); if the app is offline or outdated, the tool says so. Uses the user's minutes or credits or creates a payment; tell the user what it costs and get their agreement first. (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": {
      "text": "<text>"
    },
    "name": "send_job_apply_instruction"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe message for the apply AI, written in the user's voice
taskIdNoConversation id (taskId), from get_job_apply_client_status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that a running conversation is not interrupted but handed over at the next step or queued, that each resulting application consumes 1 Auto Apply credit at fill/submit time (once per application, free while unlimited), and that the caller must tell the user the cost and get agreement. It also states the prerequisite of a signed-in, open (or backgrounded) desktop app and the job_applications:write scope, and it describes the reply shape.

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?

Purpose is front-loaded and most sentences carry operational facts an agent needs. However, it is a single dense ~150-word paragraph, and the cost/sign-in caveats are appended in trailing parentheses rather than surfaced as scannable structure.

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?

There is no output schema, so the description supplies the return contract itself (where the message landed plus the conversation id) and directs the agent to the status tool for subsequent progress. Prerequisites, cost implications, and failure conditions (offline or outdated app) are all covered.

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 would be 3, but the description adds real meaning: taskId is the conversation id obtained from get_job_apply_client_status, and omitting it routes to the persistent Skills conversation. The text examples also convey the expected voice of the message parameter.

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 — pass one chat message to the apply AI running on the user's desktop app — and anchors it with two concrete example messages. It also distinguishes itself from the status sibling by naming get_job_apply_client_status as the follow-up for progress.

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?

Explains the default routing (persistent Skills conversation) and the condition for the override (pass taskId to target a specific conversation). It also names the follow-up tool for progress. It doesn't explicitly say when to use this instead of stop_job_apply_task or the list-management siblings, but the context makes the boundary clear enough.

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