mcp-server-steam-backlog

Overview Schema Source Related Servers Discussions Admin

Reorder Up next

backlog_reorder_next

Idempotent

Reorder the Up next queue by moving one game to a specific position or setting the order of several games, so you can control what you play first.

Instructions

<use_case> Change the order of the Up next lane (queue): move one game to a position ("put Celeste first"), or give the order of several games. </use_case> <important_notes>

Give either game + position, or order; not both.
Only games already in Up next can be ordered; add a game with backlog_set_lane(lane="next") first.
Positions are 1-based; a position past the end moves the game to the end.
If the dashboard reorders at the same moment, this re-reads once and retries; if that also collides, the outcome is conflict and nothing was changed.
Returns the previous order, so it can be undone. </important_notes> backlog_reorder_next(game="Celeste", position=1)

Input Schema

Name	Required	Description
`game`	No	Move this one game...
`order`	No	Or the new order: these Up next games first, in this order; the rest keep theirs
`position`	No	...to this 1-based position

Output Schema

Name	Required	Description
`order`	Yes
`detail`	Yes
`outcome`	Yes
`previous`	Yes
`warnings`	Yes
`protected`	Yes	false: written without a concurrency check (older backlog server)
`unresolved`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 4, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true), the description discloses non-obvious runtime behavior: a single re-read and retry on concurrent dashboard reordering, and that a second collision yields a 'conflict' outcome with no change made. It also notes the previous order is returned, enabling undo.

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?

The XML-tagged structure front-loads the use case, then constraints, then a concrete example call. Every sentence carries information — no marketing or filler — and the example anchors the syntax.

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?

For a mutation tool with an output schema available, the description covers constraints, prerequisites, concurrency semantics, and undo. Nothing an agent needs in order to invoke it correctly is missing.

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 parameter meaning is already documented and the baseline is 3. The description adds genuine value with the mutual-exclusivity rule and the note that positions are 1-based and that a position past the end appends to the end. It doesn't add format details for the game identifier itself, which the schema already covers.

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 states a specific verb and resource ('Change the order of the Up next lane') and enumerates the two operating modes (single game + position, or a full order list). This clearly distinguishes it from siblings like backlog_set_lane and backlog_get_next_queue.

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?

It explicitly says when the tool applies ('Only games already in Up next can be ordered') and names the prerequisite alternative ('add a game with backlog_set_lane(lane="next") first'). It also states that game+position and order are mutually exclusive, so the agent knows how to choose between modes.

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

Deploy Server