Mixer AI

Search your full generation history

aimixer_history_search

Read-onlyIdempotent

Search your image, video or audio history across all owned generations by model, text or date with a cursor.

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

Input Schema

Name	Required	Default
`kind`	No	all
`lang`	No	ru
`limit`	No
`query`	No
`cursor`	No
`archive`	No	active
`date_to`	No
`date_from`	No
`model_key`	No

Output Schema

Name	Required	Description	Default
`ok`	Yes
`kind`	Yes
`lang`	Yes
`items`	Yes
`archive`	Yes
`has_more`	Yes
`next_cursor`	Yes
`scan_limit_reached`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 1, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already establish that this is a safe, idempotent read operation. The description adds scope by saying it searches across all owned generations and mentions cursor-based pagination. It does not disclose defaults such as active-only archival filtering, nor does it clarify result ordering or limits beyond the schema.

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 description is a single dense sentence with no wasted language. The action and resource are front-loaded, followed by the supported filter dimensions and pagination method.

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?

The tool has nine optional parameters, 0% schema description coverage, and an output schema. The description covers the main search concept but omits important defaults and parameter semantics, including limit, lang, and archive behavior. It is adequate for initial use but incomplete for fully informed filtering.

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 parameter meaning. It maps several core parameters: media kind, model, text query, date, and cursor. However, it omits meaningful coverage for limit, lang, and the archive filter, leaving nearly half the parameters undocumented outside the schema.

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 states a specific verb and resource: search image, video, or audio history across owned generations. It adds useful filter dimensions (model, text, date, cursor). It does not explicitly distinguish itself from sibling history tools such as aimixer_history or aimixer_activity_history.

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 implied: this is the tool for searching generation history with filters. However, the description gives no explicit when-to-use guidance, no exclusions, and no comparison to sibling history tools. An agent can infer its role but must decide alternatives on its own.

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

All Mixer AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.