Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Steam app news

steam_app_news_list
Read-onlyIdempotent

Fetch a Steam app's news and announcements newest first by app ID, with cursor pagination for additional pages.

Instructions

List a Steam app's news and announcements, newest first. Requires appId. Returns a list (use cursor when paginated).

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": {
      "appId": "<appId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "steam_app_news_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNoReturn each item's full contents. By default contents are cut at 500 characters.
appIdYesRequired. Steam app id, the number in the store URL, e.g. `570` for Dota 2. A store app URL is also accepted.
feedsNoOnly these feeds, comma-separated by feed name, e.g. `steam_community_announcements`. Each item's `feed.name` says which feed it came from.
limitNoNews items per page, 1 to 100. Default: 20.
beforeNoOnly items published before this date or timestamp (UTC).
cursorNoPass `page.nextCursor` from the previous response, with the same filters, to get the next page.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description usefully adds result ordering (newest first) and a pagination cue, but says nothing about truncation defaults, filter interaction, or empty-result behavior beyond what the schema already documents.

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?

Three short sentences, front-loaded with the resource and ordering, with zero filler. The "Requires `appId`" clause marginally duplicates the schema's required list, a small redundancy against an otherwise tight definition.

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 read-only list tool with nine fully documented parameters and no output schema, the description covers the essentials: what is returned (a list), the ordering, and the pagination mechanism. It is slightly thin on how filters such as `feeds` and `before` combine with cursors, but nothing an agent strictly needs is missing.

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 carries the semantic load for appId, feeds, limit, before, cursor and the analytics parameters. The description only restates the appId requirement and the cursor convention, adding no new meaning beyond the structured field text.

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?

States a specific verb and resource ("List a Steam app's news and announcements") plus an ordering guarantee ("newest first"), which is enough for an agent to distinguish this from the reviews/achievements siblings. It does not explicitly name a neighboring alternative, so it stops short of the 5 bar.

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?

"Requires `appId`" gives a prerequisite and "use cursor when paginated" hints at pagination usage, but there is no statement of when to choose this over e.g. a general news search tool, nor any exclusion or context guidance. Usage is implied rather than directed.

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