Skip to main content
Glama

media_select

Retrieve the current media pool selection or select a specific clip before UI actions, ensuring the correct media item is targeted.

Instructions

Get the media pool selection, or select one clip (useful before UI actions).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "media_select"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, yet it discloses almost nothing: not whether the selection persists globally, what happens when an item cannot be found, whether the call errors or no-ops, or what is returned in each mode. Only the existence of a get/set split is conveyed, leaving an agent unable to predict side effects.

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?

A single short sentence with the get mode front-loaded and the set mode and motivation following. No wasted words; the only minor cost is that the parenthetical is doing work that a fuller sentence would do more explicitly.

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

Completeness2/5

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

With no annotations, no output schema, and a completely undocumented parameter, the description is the sole source of truth and it is not sufficient to call the tool confidently. The mapping of null vs. non-null item to get vs. select behavior and the meaning of a returned selection are both left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single 'item' parameter is documented nowhere. The description hints that item refers to 'one clip' and is optional (null ⇒ get, supplied ⇒ select), but never says whether it is an ID, name, or index, which is the critical detail the schema omits.

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?

States a specific verb+resource ('Get the media pool selection, or select one clip'), making the dual get/set nature clear enough for an agent to recognize what the tool is for. It does not differentiate itself from near-name siblings such as clips_select_info or media_pool, so it stops short of 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 Guidelines3/5

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

The parenthetical 'useful before UI actions' gives one implied usage context, which is more than nothing. There is no explicit when-not guidance, no mention of how this differs from related selection tools, and no statement of prerequisites, so usage is only implied.

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