GetMattered

Approve Applications

getmattered_approve_applications

Destructive

Approve up to 25 waiting applications so each is submitted to the employer’s hiring system under your name. Approval is final and uses one application credit.

Instructions

Approve applications that are waiting for the user's review (status "waiting_for_review" in getmattered_get_applications). Each approved application is submitted on the employer's own hiring system under the user's name and spends one of the user's applications. This cannot be undone: a submitted application cannot be withdrawn. Pass 1 to 25 application_ids. Approve only on the user's explicit go-ahead for those applications, such as a "yes" to a specific application. An application the plan or balance does not cover stays waiting and is reported as not sent. On a timeout or an error, call getmattered_get_applications before retrying; an approve that already went through is reported as already approved and is never sent twice. Do not use it for a job with no application yet; use getmattered_apply. Next: getmattered_get_applications to follow the submissions.

Input Schema

Name	Required	Description	Default
`application_ids`	Yes	Application ids to act on, 1 to 25 (e.g. [1550, 1551]), from getmattered_get_applications

Output Schema

Name	Required	Description
`results`	Yes
`decision`	Yes	The operation that ran: approve, reject, cancel, refine, re_prepare or set_stage.
`attempted`	Yes
`succeeded`	Yes
`notConfirmed`	Yes	True when the user declined the confirmation prompt and nothing was sent.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.10.2Oct 25, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare the destructive, non-idempotent mutation profile, but the description adds substantial consequence detail: submissions go to the employer's hiring system under the user's name, consume an application credit, and cannot be withdrawn. It also explains plan/balance handling, timeout/retry safety, and duplicate-send prevention.

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?

The description is front-loaded with the status condition and the irreversible consequence, and most sentences carry operational value. It is somewhat dense and repeats the schema's 1–25 range, but the length is justified for a high-stakes destructive action.

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?

Covers prerequisites, consent guardrails, side effects, failure recovery, and the next step, while the output schema handles return-value details. Nothing material for correct invocation is missing.

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 coverage is 100%, and the schema already documents the application_ids array, its 1–25 bound, and its source. The description reinforces the range and ties IDs to explicit approval, but it does not add new syntax or selection semantics beyond the schema.

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, defines the exact qualifying status, and distinguishes this tool from getmattered_apply and getmattered_get_applications. An agent can identify the action 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?

Explicitly says when to use it (applications waiting_for_review with the user's explicit go-ahead) and when not to use it (a job with no application yet, where getmattered_apply is correct). It also names the follow-up tool, getmattered_get_applications.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server