Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Steam app review histogram

steam_app_reviews_histogram_get
Read-onlyIdempotent

Retrieve monthly or weekly counts of positive and negative Steam app reviews by app ID to track sentiment trends and review activity over time.

Instructions

Get how many positive and negative reviews a Steam app received each month or week. Requires appId.

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_reviews_histogram_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesRequired. Steam app id, the number in the store URL, e.g. `570` for Dota 2. A store app URL is also accepted.
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered and the description needn't repeat it. The description adds the bucketing dimension (per month or per week), which is real behavioral context, but leaves open the important question of what time span the histogram covers and whether it is all-time or bounded.

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, front-loaded with the capability and then the requirement, with no padding. The second sentence is largely redundant with the schema's required field, which costs it the top score.

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?

This is a simple read tool with complete schema coverage, full annotations and no output schema, so the description only needs to convey scope and return shape. It does that much, but the phrase 'each month or week' implies a granularity choice with no corresponding parameter and no stated time range, which an agent would need to resolve before calling it confidently.

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 all four parameters, including context, llm_model and conversation_id, are already documented in the schema; the baseline of 3 applies. The description's only parameter statement, 'Requires appId,' restates the schema's own required list and adds no format or usage detail.

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?

The description states a specific verb and resource with scope: counting positive and negative reviews for a Steam app, bucketed by month or week. That is enough to distinguish it from a review listing or summary, though it never names the nearest siblings (steam_app_reviews_summary_get, steam_app_reviews_list) to sharpen the boundary.

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 only guidance is 'Requires appId,' which is a requirement already declared in the schema, not a when-to-use rule. It never says when a histogram is preferable to a review summary or a full review list, so the agent must infer the choice.

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