Skip to main content
Glama
multimedia-search-mcp

multimedia-search-mcp

list_indexers

Lists configured indexers for a media search provider and reports their status and available stats, helping you verify indexing sources before running searches.

Instructions

Lista los indexadores configurados en el proveedor y su estado.

Incluye estadísticas cuando el proveedor las publica (son opcionales).

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": "list_indexers"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose one real trait beyond structure — that statistics are optional and only present when the provider publishes them — which warns the agent about variable result shape, but it says nothing about permissions, rate limits, or failure behavior.

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?

Two short sentences with the main action front-loaded and the conditional-statistics caveat immediately after. Nothing is padded, though the parenthetical about statistics being optional could be tightened.

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?

An output schema exists, so return values need not be explained, and the tool is simple with one optional parameter. Still, the description leaves the default/omitted behavior of the sole parameter undefined, which is the main gap for a tool whose only input is that parameter.

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?

There is one optional parameter with 0% schema description coverage, so the description is the only source of meaning. It implies the provider argument scopes the listing, but never states what happens when provider is omitted or null (all providers versus a default), which is the key semantic question for this parameter.

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 and resource: listing the indexers configured in a provider plus their status. The resource ('indexadores') is distinct from sibling resources like providers or search capabilities, so an agent can tell what it returns, though it never explicitly contrasts itself with siblings such as list_providers.

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 phrase 'configurados en el proveedor' hints that the tool is scoped by provider, but there is no statement of when to call this versus list_providers or get_provider_status, and no prerequisites or exclusions.

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