Skip to main content
Glama

Restore Skipped Matches

getmattered_restore_matches
Idempotent

Restore skipped job matches by ID to undo a skip and bring matches back into your list. Closed postings cannot be restored; returns one result per ID.

Instructions

Brings skipped job matches back, which undoes getmattered_skip_matches; getmattered_unsave_matches undoes a save. A match whose posting closed cannot come back, and its id fails. Returns one result per id. Nothing is sent or spent.

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_match_ids": "<job_match_ids>"
    },
    "name": "getmattered_restore_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_match_idsYesJob match ids from getmattered_get_matches, 1 to 25 (e.g. [48213, 48214]).

Output Schema

NameRequiredDescriptionDefault
actionYesThe operation that ran, one of save, skip, unsave or restore.
resultsYes
attemptedYes
setupStepNoPresent while account setup is open: the first setup step.
succeededYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.13.2
    • changedOutput schema / properties / action / description
      Previous value: -"The operation that ran: save, skip, unsave or restore."New value: +"The operation that ran, one of save, skip, unsave or restore."
    • addedOutput schema / properties / setupStep
      Added value: +{
      +  "description": "Present while account setup is open: the first setup step.",
      +  "type": "string"
      +}
  2. Addedv1.10.2

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false, idempotentHint=false-style safety and openWorldHint=false; the description usefully adds that nothing is sent or spent and that closed postings cause per-id failure. That is real value beyond the annotations, but idempotency and the exact batch outcome on partial failure aren't spelled out beyond 'one result per id'. Solid but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action, then the inverse relationship, then the failure and side-effect caveats. No filler.

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 single-parameter batch mutation, it covers the action, the inverse, the failure mode, and the absence of external side effects; an output schema exists so return shape needn't be described. Only the partial-failure payload behavior is slightly underspecified.

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 already documents job_match_ids as an integer array of 1–25 ids sourced from get_mattered_get_matches. The description adds only the per-id result/failure semantics, which is marginal beyond the schema baseline.

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?

Specific verb (brings back) plus resource (skipped job matches), and it explicitly positions itself against the sibling it reverses, getmattered_skip_matches. An agent can distinguish this from getmattered_unsave_matches without reading either schema.

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 states the inverse relationship plainly: this undoes skip_matches, while unsave_matches undoes a save, which effectively routes the agent to the right tool. It also gives a precondition (a closed posting cannot be restored and its id fails). It stops short of an explicit 'use when the user wants to un-skip' trigger phrasing, so a 4 rather than a 5.

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