Skip to main content
Glama

OpenAny

Web Search (Basic, no extraction)

youcom_post_v1_search

Search web and news results with all page-extraction options disabled. Uses the caller's OpenAny gateway credentials. Charges and authorization are determined by the gateway.

Input Schema

NameRequiredDescriptionDefault
countNoSpecifies the maximum number of search results to return per section (the sections are `web` and `news`. See the JSON response to visualize them).
queryYesThe search query used to retrieve relevant results from the web. You can also include [search operators](https://you.com/docs/guides/search/search-operators) to refine your search.
offsetNoIndicates the `offset` for pagination. The `offset` is calculated in multiples of `count`. For example, if `count = 5` and `offset = 1`, results 5–10 will be returned. Range `0 ≤ offset ≤ 9`.
countryNoThe country code that determines the geographical focus of the web results.
languageNoThe language of the web results that will be returned (BCP 47 format).
knowledgeNoRequests knowledge results alongside web and news search.
safesearchNoConfigures the safesearch filter for content moderation. This allows you to decide whether to return NSFW content or not.
boost_domainsNoA list of domains to boost in search ranking. Matching results from these domains receive a fixed relative ranking boost, but this is not a filter. If the boosted domains do not have matching results, results from other domains can still appear. Supports up to 500 domains. Can be combined with `exclude_domains`. Cannot be combined with `include_domains`. Passing both `boost_domains` and `include_domains` will return a `422` error.
exclude_domainsNoA list of domains to exclude from search results. Results from these domains will be filtered out. Supports up to 5000 domains. Cannot be combined with `include_domains`; passing both will return a `422` error.
include_domainsNoA list of domains to restrict search results to. Only results from these domains will be returned. Supports up to 500 domains. This is a strict allowlist, not a boost — results are limited exclusively to the specified domains. Cannot be combined with `exclude_domains`; passing both will return a `422` error.
strict_operatorsNoEnforce search operators such as quoted phrases and `site:` exactly. By default, when a query's operators match no pages, the search relaxes them and returns the closest matches. Has no effect with `extraction_mode: "highlights"`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description bears the full burden. It usefully discloses that the tool uses the caller's OpenAny gateway credentials and that charges/authorization are determined by the gateway. However, it omits other behavioral details such as whether the operation is read-only, the response shape, pagination behavior, or rate limits.

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?

The description is three sentences and front-loads the core purpose. The billing sentences earn their place by clarifying credential and cost behavior, though the text could be slightly tighter.

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?

For an 11-parameter search tool with no annotations and no output schema, the description is thin. It lacks information about the response format (web and news sections), result limits, pagination behavior, and any rate or cost details beyond the gateway note.

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 schema already documents all 11 parameters in detail. The description adds no parameter-specific meaning beyond the schema; it only mentions that extraction options are disabled, which does not correspond to any schema 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?

The description states a specific verb and resource: 'Search web and news results.' It adds a scope qualifier ('all page-extraction options disabled'), which distinguishes it from a hypothetical extraction-enabled variant. However, it does not explicitly differentiate from the sibling youcom_post_v1_answer or other search tools in the list.

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?

The description gives no explicit when-to-use guidance, no when-not-to-use conditions, and no named alternatives. The phrase 'page-extraction options disabled' hints that a different tool should be used when extraction is needed, but it never names that alternative or explains the trade-off.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.