Skip to main content
Glama

add_search_result_to_favorites

Add a specific track from recent search results to favorites by entering its result number.

Instructions

Adds a specific track number from the recent search results to favorites.

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": {
      "number": "<number>"
    },
    "name": "add_search_result_to_favorites"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations provided, the description lacks behavioral details. It fails to disclose crucial behavioral traits for a mutation tool, such as whether the tool handles duplicates (e.g., if the track is already favorited), what happens if the track number is invalid, or if the favorite list updates immediately.

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?

The definition is a single, focused sentence that conveys the full scope of the tool efficiently without any wasted language.

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?

It is a minimum viable definition. It tells the agent *what* it does and *where* the input must come from (recent search results). However, for a mutation tool, it is insufficient because it provides no guarantees on success or failure states.

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?

The input schema defines 'number' as an integer, and the description clarifies it means a 'track number'. While this adds minor semantic context beyond the schema, the 0% schema description coverage means the description needs to do heavy lifting, and it doesn't specify the required format or bounds of this number.

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?

The description is highly specific, using the verb 'Adds' and clearly defining the resource being operated on ('a specific track number') and the destination ('to favorites'). This makes it very easy for an agent to distinguish this tool from similar playback or search tools.

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?

By specifying that the track must come 'from the recent search results,' the description provides an important context constraint on usage. It implicitly guides the user away from providing arbitrary track numbers, which is helpful.

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