Skip to main content
Glama
kimi-search-mcp
by Wildare-98

Kimi Web Search Pro

kimi_search_pro

Search the web and return ranked page excerpts with source URLs and authority for QA, RAG, research, and reports; filter by site and publication date.

Instructions

Search the web with Kimi Search Pro. Returns relevant page excerpts ranked by relevance, with source URLs and authority. Best for web QA, RAG, research, and reports. Supports site and publication-date filters.

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": {
      "text_query": "<text_query>"
    },
    "name": "kimi_search_pro"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results, 1-20. Default 5.
sitesNoRestrict results to up to 5 sites, combined with OR. Example: ["gov.cn", "miit.gov.cn"].
text_queryYesSearch query. Include specific entities, dates, and source constraints when relevant.
time_windowNoPublication date range. start must not be after end.
timeout_secondsNoKimi API search timeout in seconds, 1-60. Default 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the return shape (ranked excerpts, source URLs, authority) and that site/date filtering is supported, which is useful. It says nothing about authentication, rate limits, cost, or what happens on timeout, and the timeout parameter's behavioral implications are left entirely to 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and the return value, then the use cases and filters. No filler, though the "Kimi Search Pro" branding repetition in the first sentence is marginally redundant with the tool title.

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

Completeness4/5

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

No output schema exists, but the description compensates by describing what is returned, and the fully documented input schema handles the five parameters including the nested date range. The main remaining gap is sibling differentiation, which matters given kimi_search and kimi_fetch are present.

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 100%, so each parameter is already documented with ranges, defaults, formats, and examples. The description only restates that site and publication-date filters exist, adding no semantics beyond the schema; baseline 3 applies.

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 ("Search the web with Kimi Search Pro") and adds what comes back: page excerpts ranked by relevance with source URLs and authority. It does not, however, distinguish this from the sibling kimi_search, so an agent cannot tell from the text alone why 'Pro' exists or when it is the right pick.

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?

"Best for web QA, RAG, research, and reports" implies usage contexts, which is more than nothing. But there are no exclusions, no prerequisites, and no routing guidance versus kimi_search or kimi_fetch, leaving the agent to guess between siblings.

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