GAMES.GG

Remove a saved guide

unsave_guide

DestructiveIdempotent

Use when the user asks to remove a saved or bookmarked guide from their GAMES.GG account. guide is the guideSlug from search_guides, or the guide value from my_saved_guides or my_code_follows; pass the search result's locale. Returns what changed and the guide's GAMES.GG url.

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": {
      "guide": "<guide>"
    },
    "name": "unsave_guide"
  }
}

Input Schema

Name	Required	Description	Default
`guide`	Yes	The guideSlug from search_guides, or the guide value from my_saved_guides or my_code_follows.
`locale`	No	The locale of that search_guides result.

Output Schema

Name	Required	Description
`url`	Yes
`saved`	Yes
`title`	Yes
`changed`	Yes	false when the account already had this state.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the agent knows this mutates saved state and that repeats are safe. The description adds only that it returns what changed plus the GAMES.GG url, and says nothing about whether the removal is reversible or what happens when the guide was never saved — behavior that matters for a destructive call.

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 with the trigger condition front-loaded and no filler. The final sentence about return values is slightly redundant given an output schema exists, but overall the text is tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter destructive removal with full schema coverage, explicit safety annotations and an output schema, the description covers the trigger, both argument sources and the response shape. Nothing an agent needs in order to call it correctly 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 both properties are already documented, and the description largely repeats the schema wording for `guide`. The one genuine addition is the directive to pass the locale from the same search result, but it does not clarify whether locale is optional or what happens if omitted.

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?

States a specific verb and resource ("remove a saved or bookmarked guide") scoped to the user's GAMES.GG account, which cleanly separates it from the sibling unsave_game and from save_guide. An agent can identify the operation without opening the schema.

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 opening clause gives an explicit trigger ("Use when the user asks to remove a saved or bookmarked guide") and the second sentence routes the agent to the correct upstream tools for both arguments. It stops short of naming the inverse/alternative (save_guide) or stating a when-not condition, so it is strong context without full exclusions.

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

All GAMES.GG tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?