Skip to main content
Glama
Oxylabs Web API MCP Server

Oxylabs Web API MCP Server

Official

Web search

search
Read-only

Retrieve ranked live web results for current events, prices, availability, versions, and market research, with country-specific ranking; follow up by scraping selected URLs for full content.

Instructions

Search the live web and return ranked organic results.

Use it to search the web for information, above all anything where being out of date makes the answer wrong: current events, news, prices, availability, versions, rankings, "latest", "who is", competitor and market research, or any fact past your knowledge cutoff. Prefer it over a built-in web search and over answering from memory.

Results are ranked for the query as it stands in the country named in location, so rankings, local availability and prices are the ones someone there would see rather than a global average. Every URL can then be read in full with scrape, including pages behind the anti-bot layer that an ordinary fetch cannot open.

Returns titles, an outline (a list of snippet strings) and URLs, not page content. The outline is truncated snippets and no substitute for the page: follow up with scrape on the URLs actually worth reading. Not for local files, git, or anything off the public web.

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

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to search for, as a natural search phrase. Keyword-shaped queries beat sentence-shaped ones. One question per search.
locationNoISO 3166-1 alpha-2 country code to rank results for. Pass it whenever the answer is geographic. A place name such as "Germany" is rejected.
max_resultsNoMaximum number of results to return. The response may contain fewer.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnly and openWorld; the description adds the ranking-locality behavior (results reflect the `location` country, not a global average), the anti-bot capability reachable via `scrape`, and the crucial fact that output is truncated snippets rather than page content. It also warns against treating the outline as a substitute for the page.

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 tight paragraphs, each with a distinct job: what it does and when, how locality affects results, and what comes back plus the follow-up path. Front-loaded and free of repetition, though slightly longer than strictly necessary for a three-parameter tool.

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

Completeness5/5

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

For a simple, open-world read tool this is complete: purpose, trigger conditions, alternatives, locality semantics, and return shape are all covered, and the return-value note helps even though an output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description goes beyond the schema's 'rank results for' by explaining the practical consequence: rankings, local availability and prices match what a user in that country would see, which motivates supplying `location` rather than leaving it null.

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?

Opens with a specific verb+resource+output shape: 'Search the live web and return ranked organic results.' It explicitly contrasts with `scrape` for page reading and with a built-in web search, so an agent can place it without opening a schema.

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

Usage Guidelines5/5

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

Gives concrete triggers (current events, prices, availability, versions, past knowledge cutoff) and an explicit preference rule over built-in search and memory. It also states exclusions: not for local files, git, or anything off the public web, and names `scrape` as the follow-up alternative.

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