Skip to main content
Glama

AIApply

Pause or resume AIApply applications

pause_resume_applications
DestructiveIdempotent

Use this when the connected user asks to stop or restart AIApply applying for them. action="pause" stops all automatic applying and is destructive: call it without confirmed, show the user what will stop, ask them, then call again with confirmed=true. action="resume" restarts applying and spends credits, so confirm it the same way. To stop applications to particular roles only, this is the wrong tool — that is a preference change the user makes in AIApply. 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": {
      "action": "<action>"
    },
    "name": "pause_resume_applications"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYespause stops all automatic applying; resume restarts it.
confirmedNoTrue only after the user has explicitly agreed to this change.

Output Schema

NameRequiredDescriptionDefault
errorNoTrue when the change could not be made.
reasonNoWhy nothing changed, when nothing did.
appliedNoTrue only when the queue changed.
messageYes
queue_statusNoThe status the queue now holds.
user_messageNoShow this to the user rather than message.
previous_statusNoThe status it held before.

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?

Beyond annotations that already flag destructiveHint and non-readOnly, the description discloses the two-step confirmation protocol verbatim (call without confirmed, show the user what will stop, ask, then re-call with confirmed=true) and notes that resume spends credits. It also explains prerequisite state: an unauthenticated caller is prompted to sign in, and a missing permission triggers an allow prompt — exactly the context annotations cannot convey.

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?

It is front-loaded with the trigger condition and the destructive confirmation flow before the secondary auth notes. The two trailing auth sentences are somewhat repetitive ("it also needs a permission the user grants; if it was not granted..."), but no sentence is filler.

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?

The tool is a destructive, credit-spending, auth-gated toggle with an output schema, and the description covers the confirmation protocol, cost side effect, account/permission prerequisites, and the mis-scope case. Nothing an agent needs in order to call it safely is left out.

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 adds real meaning by tying `confirmed` to a specific sequence of events (only after the user has explicitly agreed, following a preview of what will stop) and by flagging the credit-spend consequence of `action=resume` that the schema omits.

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?

The description names the specific verb pair (pause/resume) and the resource (automatic applying for the connected user), so the action is unambiguous. It also draws a clear boundary against a same-sounding but different operation: stopping applications to particular roles is a preference change, not this tool.

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?

It gives an explicit when-to-use trigger (user asks to stop or restart applying) and an explicit when-not (per-role stopping belongs to the preference flow in AIApply). The alternative is described as a user-side preference change rather than pointing at a callable sibling like open_auto_apply_preferences, so the redirect is directional but not fully actionable.

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