Skip to main content
Glama
TMHSDigital

Steam MCP Server

by TMHSDigital
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

steam_updateWorkshopItem

Update metadata for an existing Steam Workshop item, including title, description, visibility, and tags. Set confirm=true to apply changes after a dry run.

Instructions

MUTATES LIVE WORKSHOP ITEM METADATA. Default dry_run=true; requires confirm=true to send. Update metadata for an existing Steam Workshop item (title, description, visibility, tags) via the partner API. Does not change the store page listing. Requires a publisher API key with server IP allowlisted. File content updates require the SDK.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoReplace the item's tags with this list
appidYesSteam application ID
titleNoNew title for the item
confirmNoRequired true when dry_run is false. Refuses otherwise.
dry_runNoIf true (default), return the planned request without contacting Steam
visibilityNoVisibility: 0=Public, 1=FriendsOnly, 2=Private, 3=Unlisted
publishedfileidYesWorkshop item's published file ID
file_descriptionNoNew description for the item

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.0
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "Required true when dry_run is false. Refuses otherwise.",
+  "type": "boolean"
+}
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "If true (default), return the planned request without contacting Steam",
+  "type": "boolean"
+}
  2. First observedv0.7.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It clearly discloses the mutation behavior, the dry-run safety mechanism, the confirm requirement, and the fact that store page listing is not changed. It could add more about side effects (e.g., whether existing metadata is replaced or merged), but the dry-run/confirm flow is a strong behavioral disclosure.

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 compact and front-loaded with the most important behavioral warning (MUTATES, dry_run, confirm). Every sentence adds value, though the all-caps opening is slightly noisy. It is efficient and well-structured.

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 mutation tool with no annotations and no output schema, the description covers the key operational context: mutation, dry-run, confirm, API key requirement, and what it does not do. It could mention the return value or error behavior, but the essential context for calling it correctly is present.

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%, so the schema already documents all 8 parameters. The description adds context about the dry_run/confirm interaction and the metadata fields, but it doesn't add much beyond what the schema already says. Baseline 3 is appropriate.

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 opens with 'MUTATES LIVE WORKSHOP ITEM METADATA' and then specifies the exact fields (title, description, visibility, tags) and the API (partner API). It also distinguishes itself from store page listing changes and file content updates, which helps separate it from sibling tools like steam_uploadWorkshopItem.

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?

The description explicitly states the default dry_run=true and the requirement for confirm=true to send, which is critical usage guidance. It also names the alternative for file content updates ('File content updates require the SDK') and notes the prerequisite of a publisher API key with allowlisted server IP, giving clear when-to-use and when-not-to-use context.

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

Deploy Server

Other Tools