GetMattered

Restore Skipped Matches

getmattered_restore_matches

Idempotent

Brings back skipped matches. A closed posting cannot be restored.

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

Name	Required	Description	Default
`job_match_ids`	Yes	Job match ids from getmattered_get_matches, 1 to 25 (e.g. [48213, 48214]).

Output Schema

Name	Required	Description
`action`	Yes	The operation that ran, one of save, skip, unsave or restore.
`results`	Yes
`attempted`	Yes
`setupStep`	No	Present while account setup is open: the first setup step.
`succeeded`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 8, 2026

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."

changedOutput schema / properties / setupStep / description

Previous value: -"Set while account setup is open: the step to take first."New value: +"Present while account setup is open: the first setup step."

Changed1 schema field changedNov 6, 2026

addedOutput schema / properties / setupStep

Added value: +{
+  "description": "Set while account setup is open: the step to take first.",
+  "type": "string"
+}

AddedOct 25, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare not-read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds one genuinely useful rule beyond them — closed postings cannot be restored — which warns of a partial-failure case. It says nothing about what state the restored matches return in, though idempotency is already annotated.

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?

Two short sentences, mutation intent front-loaded and the failure constraint immediately after. No filler, though the second sentence is cryptic enough that a few more words of context would not be waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and the single parameter is documented, so the description needn't explain returns. However, for a state-mutating batch tool it omits what happens to ids that were never skipped or don't exist, leaving error behavior unclear.

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 description coverage is 100% and the parameter is fully documented there, including the 1–25 batch limit and example ids. The description adds no parameter meaning, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Brings back skipped matches" states a specific verb and resource and is clearly the inverse of getmattered_skip_matches in the sibling list, so an agent can place it in the lifecycle. It stops short of naming the counterpart tool explicitly, so the differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description gives no when-to-use guidance: it never mentions getmattered_skip_matches as the inverse operation, nor when restoration is appropriate versus re-fetching matches. The only pointer to a related tool (getmattered_get_matches as the id source) lives in the schema, not the description.

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

All GetMattered tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.