Skip to main content
Glama

query_workshop_items

Query Steam Workshop items for a game using its App ID. Filter by search text, sort by subscriptions or recency, and optionally include tags.

Instructions

Query Steam Workshop items for a game.

Requires STEAM_API_KEY.

Return Format

{"success": bool, "message": str, "data": {"items": [...], "total": int}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idYesSteam App ID to query workshop for.
queryNoSearch text for workshop items.
countNoMax items to return.
sort_byNoSort order. Options: 'score', 'trend', 'mostrecent', 'mostsubscribed', 'mostfavorited', 'mostunsubscribed'.mostsubscribed
return_tagsNoInclude item tags in results.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

With no annotations provided, the description must carry behavioral disclosure. It indicates a read-only query via the word 'Query' and includes the return format, but lacks details on side effects, rate limits, or authentication specifics beyond the API key requirement.

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 concise, consisting of two short sentences plus a return format block. It is front-loaded with the core purpose and requirements, with no superfluous information.

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?

Given the tool has five parameters and an output schema, the description covers the basics but omits context such as pagination behavior, error handling, or how to provide the API key. It is adequate but not thorough.

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%, so the baseline is 3. The description adds no additional parameter meaning beyond what the schema already provides, but it does include the return format which indirectly informs parameter use.

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 'Query Steam Workshop items for a game' uses a specific verb and resource, clearly distinguishing it from sibling tools like get_app_details or search_store which target different Steam features.

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

Usage Guidelines3/5

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

The description mentions the requirement 'Requires STEAM_API_KEY' but provides no explicit guidance on when to use this tool versus alternatives or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sandraschi/steam-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server