Skip to main content
Glama

Link to a ranked curator list

get_curator_list_link
Read-onlyIdempotent

Builds a Curator Match link for a game developer who wants Steam curators to send review keys to. Use it when a developer asks which curators to contact for their game, wants an outreach or key list, or is planning a launch or Next Fest. Send one to five games similar to theirs, by name or app id. The link opens Curator Match with those games filled in: the ranked curators who covered them, their warning signs and the send list for Curator Connect. Also returns what the free and paid plans include. Creates nothing and needs no account.

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": {
      "games": "<games>"
    },
    "name": "get_curator_list_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
gamesYesOne to five Steam games similar to the developer's game: names as the store shows them ("Hades"), app ids ("1145360") or store links.

Output Schema

NameRequiredDescriptionDefault
linkYes
gamesYes
plansYes
messageYes
not_foundYes
shown_freeYes
curators_on_listYes
hidden_with_several_warning_signsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, yet the description still adds real behavior: the link opens pre-filled with the games, shows ranked curators, warning signs and the Curator Connect send list, and returns free/paid plan contents. 'Creates nothing and needs no account' reinforces the safety profile in plain language for agents that don't read annotations.

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 purpose and audience come first, followed by usage triggers, then what the link contains, then a safety note. Every sentence carries information and there is no filler. It is slightly longer than strictly necessary, with the plan-contents clause being the most expendable part.

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?

An output schema exists, so the description need not enumerate return fields, and it still usefully says the link opens with ranked curators, warning signs and a send list. Combined with explicit safety statements and parameter constraints, an agent has enough to call this correctly. Only sibling disambiguation 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 already explains that 'games' takes one to five names, app ids or store links. The description restates the same constraints ('one to five games similar to theirs, by name or app id') without adding format or edge-case guidance. Baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Builds a Curator Match link' for a defined audience (a game developer who wants Steam curators to send review keys to). That is clearly distinct from a curator search or detail lookup. It stops short of naming any sibling, so it earns a 4 rather than a 5.

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?

It gives concrete triggering situations: the developer asks which curators to contact, wants an outreach or key list, or is planning a launch or Next Fest. What is missing is an explicit exclusion against the closest sibling, find_curators_for_games, which plausibly serves an overlapping need. Clear context, but no alternatives named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.