Skip to main content
Glama
Octen-Team

octen-mcp

Official
by Octen-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Web Search

search
Read-only

Query the live web for ranked results (title, URL, snippet) to answer a single focused lookup. Filter by news topic, language, time window, or domain.

Instructions

Search the live web and return ranked results (title, url, snippet) — fast, fresh, real-time web search for one focused lookup. Set topic to news for news-focused results. Pass highlight to get a ranked snippet per result, or full_content to pull the cleaned page body inline (heavier — costs more context). Narrow with domain / text include-exclude filters, a language filter (ISO 639-1 codes), and a time window (published/crawled start_time/end_time, or a relative time_range). Set include_images to return image URLs per result.

USE FOR a single focused lookup: one fact, one entity, one document. If the question spans several independent subtopics, load and use broad_search instead — a sequence of search calls is slower and gives worse coverage than one fan-out. To read a page you already have the URL for, use extract.

keywords: web search, search the web, look up, find, check, fact, current information, latest, news, source, url, real-time

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of results to return (1-100). Default 5.
queryYesNon-empty search query. Max 500 chars.
topicNoSearch category: `general` for broad web search, `news` for news-focused results. Default general.general
formatNoFormat of returned content. Default text.text
timeoutNoRequest timeout in seconds (1-60). Defaults to 30s if unset.
end_timeNoUpper bound for the time window, ISO 8601.
languageNoLanguages to filter results by, as ISO 639-1 codes. Empty = no filter.
highlightNoReturn a ranked highlighted snippet per result. Omit to use the server default.
safesearchNoAdult-content filter. Default strict.strict
start_timeNoLower bound for the time window, ISO 8601 (e.g. '2025-01-01T00:00:00Z').
time_basisNoWhich timestamp the time window filters against: page `published` date, last `crawled` date, or `auto`. Default auto.auto
time_rangeNoRelative time window (e.g. `week`, `month`). Mutually exclusive with `start_time`/`end_time` — if both are given, the absolute range wins.
exclude_textNoDrop results whose content contains any of these strings. Max 5, each ≤30 chars.
full_contentNoReturn the cleaned full page body per result. Heavier than `highlight` — use only when the snippet isn't enough. Omit to use the server default (off).
include_textNoOnly return results whose content contains all of these strings. Max 5, each ≤30 chars.
include_imagesNoReturn image URLs (and a cover image) found on each result page.
exclude_domainsNoDrop results from these domains. Max 1200, each ≤60 chars.
include_domainsNoOnly return results from these domains (e.g. 'arxiv.org'). Max 1200, each ≤60 chars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.2
    • changedInput schema / properties / query / description
      Previous value: -"Search query. Max 500 chars."New value: +"Non-empty search query. Max 500 chars."
    • addedInput schema / properties / query / minLength
      Added value: +1
  2. Changed7 schema fields changedv0.5.0
    • changedInput schema / properties / exclude_domains / description
      Previous value: -"Drop results from these domains. Max 150, each ≤30 chars."New value: +"Drop results from these domains. Max 1200, each ≤60 chars."
    • changedInput schema / properties / exclude_domains / items / maxLength
      Previous value: -30New value: +60
    • changedInput schema / properties / exclude_domains / maxItems
      Previous value: -150New value: +1200
    • changedInput schema / properties / include_domains / description
      Previous value: -"Only return results from these domains (e.g. 'arxiv.org'). Max 1000, each ≤30 chars."New value: +"Only return results from these domains (e.g. 'arxiv.org'). Max 1200, each ≤60 chars."
    • changedInput schema / properties / include_domains / items / maxLength
      Previous value: -30New value: +60
    • changedInput schema / properties / include_domains / maxItems
      Previous value: -1000New value: +1200
    • removedInput schema / properties / include_videos
      Removed value: -{
-  "default": false,
-  "description": "Return video URLs found on each result page.",
-  "type": "boolean"
-}
  3. Changed1 schema field changedv0.4.2
    • changedInput schema / properties / timeout / description
      Previous value: -"Request timeout in seconds (1-60)."New value: +"Request timeout in seconds (1-60). Defaults to 30s if unset."
  4. Addedv0.3.6
  5. Removedv0.3.5
  6. Addedv0.3.4
  7. Removedv0.3.3
  8. Addedv0.2.2

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only and open-world safety, so the burden is lower. The description adds real operational context: full_content is 'heavier — costs more context', time_range vs absolute range conflict resolution ('absolute range wins'), and that highlight yields a ranked snippet. It stops short of describing result ordering or pagination.

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?

Long but front-loaded: capability and return shape come first, then parameter highlights, then a clearly delimited USE FOR routing block. The trailing keyword list is boilerplate that dilutes rather than informs, which is the only real excess.

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 an 18-parameter tool with nested objects and no output schema, the description covers the capability, the return shape (title, url, snippet), the heavy-vs-light trade-off, and the sibling routing. An agent has everything needed to choose and call it correctly.

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 the schema carries most of the load and baseline is 3. The description still adds narrative meaning: it groups filters (domain/text include-exclude, language ISO 639-1, published vs crawled time window) and flags the cost trade-off between highlight and full_content rather than just restating field names.

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?

States a specific verb and resource ('Search the live web and return ranked results') with the return shape (title, url, snippet) and scope ('one focused lookup'). It explicitly distinguishes itself from siblings: 'broad_search' for fan-out questions and 'extract' for reading a known URL.

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?

Explicit routing: USE FOR a single focused lookup (one fact, entity, document). Names two alternatives by name and the conditions that select them — broad_search when subtopics are independent, extract when a URL is already held. Nothing is left to inference.

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