Skip to main content
Glama

add_game_review

Create or edit a game review as a draft, then publish it when the review has at least 800 characters of text and a 1–10 score.

Instructions

Write or update your review. Saved as a draft unless publish=true. Publishing needs 800+ characters of text and an overall score (1-10). body is plain text (blank lines split paragraphs) or HTML. title 5-100 chars. pros/cons: JSON array or one per line. Re-running edits the same review.

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": {
      "slug": "<slug>",
      "body": "<body>"
    },
    "name": "add_game_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
consNo
prosNo
slugYes
scoreNo
titleNo
publishNo
wait_msNo
languageNo
spoilersNo
completionNo
acquisitionNo
collection_idNo
mature_contentNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv2.1.0
    • addedInput schema / properties / acquisition
      Added value: +{
      +  "default": "",
      +  "title": "Acquisition",
      +  "type": "string"
      +}
    • addedInput schema / properties / collection_id
      Added value: +{
      +  "default": "",
      +  "title": "Collection Id",
      +  "type": "string"
      +}
    • addedInput schema / properties / completion
      Added value: +{
      +  "default": "",
      +  "title": "Completion",
      +  "type": "string"
      +}
    • addedInput schema / properties / cons
      Added value: +{
      +  "default": "",
      +  "title": "Cons",
      +  "type": "string"
      +}
    • removedInput schema / properties / feed
      Removed value: -{
      -  "default": false,
      -  "title": "Feed",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / mature
      Removed value: -{
      -  "default": false,
      -  "title": "Mature",
      -  "type": "boolean"
      -}
    • addedInput schema / properties / mature_content
      Added value: +{
      +  "default": false,
      +  "title": "Mature Content",
      +  "type": "boolean"
      +}
    • removedInput schema / properties / platform
      Removed value: -{
      -  "default": "",
      -  "title": "Platform",
      -  "type": "string"
      -}
    • addedInput schema / properties / pros
      Added value: +{
      +  "default": "",
      +  "title": "Pros",
      +  "type": "string"
      +}
    • changedInput schema / properties / publish / default
      Previous value: -trueNew value: +false
    • addedInput schema / properties / score
      Added value: +{
      +  "default": "",
      +  "title": "Score",
      +  "type": "string"
      +}
    • changedInput schema / properties / wait_ms / default
      Previous value: -3000New value: +0
  2. First observedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does a fair job: it discloses the default non-publishing behavior, the hard minimums that gate publishing, accepted body formats, and idempotent re-run semantics. It says nothing about permissions, side effects on existing reviews (e.g., whether omitted fields are cleared), or how spoilers/mature_content affect visibility.

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 most consequential facts (draft by default, publishing requirements) are front-loaded, and nearly every sentence adds new information. The telegraphic fragments are efficient but slightly terse, making constraints like title length easy to skim past.

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?

An output schema exists, so return values need not be explained. However, for a 14-parameter mutation tool with zero annotation coverage and zero schema descriptions, eight undocumented parameters leave the definition short of what an agent needs to call 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 0%, so all 14 parameters depend on this text. The description explains body (plain text vs HTML, blank lines as paragraph breaks), title (5-100 chars), pros/cons (JSON array or one per line), score (1-10), and publish. It leaves slug, wait_ms, language, spoilers, completion, acquisition, collection_id, and mature_content entirely undefined, which is a substantial gap for a 14-parameter tool.

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?

"Write or update your review" gives a specific verb and resource, and the description clarifies that a re-run edits the same review rather than creating a duplicate. It stops short of distinguishing itself from siblings like add_game_content or set_game_rating, so an agent must infer that this is the review-specific path.

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

Usage Guidelines4/5

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

The draft-vs-publish condition is stated explicitly ("Saved as a draft unless publish=true"), which is the main usage decision an agent must make. It also states the prerequisites for publishing (800+ characters, an overall score 1-10). No alternatives or exclusions relative to sibling tools are named.

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