Skip to main content
Glama
fatwang2

Search1API MCP Server

search

Retrieve web results from multiple search engines, with optional full-page crawling and site/time filters.

Instructions

Web search tool

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query, be simple and concise
max_resultsNoMaximum number of results to return
search_serviceNoSpecify the search engine to use. Choose based on your specific needsgoogle
crawl_resultsNoNumber of results to crawl for full webpage content, useful when search result summaries are insufficient for complex queries
include_sitesNoList of sites to include in search. Only use when you need special results from sites not available in search_service
exclude_sitesNoList of sites to exclude from search. Only use when you need to explicitly filter out specific domains from results
time_rangeNoTime range for search results, only use when specific time constraints are required
Behavior2/5

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

No annotations are present, and the description does not disclose behavioral traits like return value, pagination, or limitations. The schema provides parameter details, but the description itself adds no behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is extremely concise (three words), but it sacrifices necessary information. It is under-specified for a tool with 7 parameters and no annotations.

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

Completeness2/5

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

Given the complexity (7 parameters, no output schema, no annotations), the description is incomplete. It does not explain return values or other contextual details that are missing from the schema.

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 the baseline is 3. The description does not add additional meaning beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Web search tool' indicates the tool performs web searches, but it is generic and does not differentiate from siblings like 'news' or 'crawl'. The purpose is clear but lacks specificity.

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 is provided on when to use this tool vs alternatives such as 'news' or 'crawl'. The description offers no context for selecting between sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fatwang2/search1api-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server