Skip to main content
Glama
Sign In
my-minimax-mcp

my-minimax-mcp

by wongo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

minimax_web_search

Retrieve web search results including titles, links, snippets, and related queries using MiniMax AI.

Instructions

Search the web using MiniMax AI. Returns results with titles, links, snippets, and related searches.

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": {
      "query": "<query>"
    },
    "name": "minimax_web_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description bears full burden. It mentions output fields but omits critical behavioral traits such as rate limits, authentication needs, handling of empty results, or whether the operation is read-only. The description is minimally transparent.

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 consists of two short, front-loaded sentences with no wasted words. Every sentence conveys distinct information: the tool's purpose and its output structure.

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?

For a simple tool with one parameter, the description covers purpose and basic output. However, it fails to specify result count, pagination, possible errors, or behavioral constraints. Given no output schema or annotations, more detail would be beneficial.

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 coverage is 100% (single 'query' parameter described as 'Search query'). The description adds value by listing output fields but does not further elaborate on the query parameter itself. Baseline 3 is appropriate.

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 clearly states the tool's action (search the web using MiniMax AI) and what it returns (titles, links, snippets, related searches). It sufficiently distinguishes from sibling tools like minimax_chat or minimax_understand_image.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. No explicit context on when not to use it, prerequisites, or comparisons with sibling tools like minimax_plan or minimax_generate_code.

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

Deploy Server

Other Tools