Skip to main content
Glama

set_featured

Promote a play to featured status so it gets first-person videos when the match is produced, or remove it; this overrides automatic curation and persists through re-scoring.

Instructions

Promote a play to the featured ones (they get first-person videos when the match is produced) or remove it from them. Overrides the automatic curation and survives re-scoring.

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": {
      "highlight_id": "<highlight_id>",
      "featured": "<featured>"
    },
    "name": "set_featured"
  }
}

Input Schema

NameRequiredDescriptionDefault
featuredYes
highlight_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already convey that this is a non-read-only, non-destructive, closed-world mutation, so the description adds real value on top: it discloses that the setting overrides automatic curation and persists across re-scoring, plus the downstream consequence that featured plays receive first-person videos at production time. It stops short of noting idempotency or failure behavior, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, action stated first, with a parenthetical that earns its place by explaining the consequence and a final clause covering override semantics. Nothing is redundant.

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 two-parameter mutation with annotations and an output schema, the description covers purpose, effect, and persistence adequately. The main remaining gap is confirmation of what highlight_id must reference and what happens if the play does not exist.

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 the description must carry the parameter meaning, and it only partly does. The phrasing 'promote ... or remove it from them' effectively explains the boolean 'featured', but the identifier parameter is called 'play' while the schema calls it highlight_id, leaving a terminology gap about what value to supply.

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 names a specific verb pair (promote / remove) and the resource (a play, i.e. a highlight) along with the 'featured' state it manipulates. It is clearly distinct from siblings like create_highlight, edit_highlight or delete_highlight because it describes a curation-state toggle rather than content mutation.

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?

Usage is only implied: the reader infers that setting the flag on promotes and off removes, and that this tool is for overriding automatic curation. There is no explicit statement of prerequisites (the highlight must already exist), no when-to-use framing versus edit_highlight, and no note about who may perform the override.

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