Skip to main content
Glama
Octen-Team

octen-mcp

Official
by Octen-Team

search

Search the live web and get ranked results with titles, URLs, and snippets. Filter by domain, text, or publication date; optionally retrieve highlighted excerpts or full page content.

Instructions

Search the live web with Octen and return ranked results (title, url, snippet). 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 and a time window (published/crawled start_time/end_time, or a relative time_range). Set include_images / include_videos to return media URLs per result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of results to return (1-100). Default 5.
queryYesSearch 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).
end_timeNoUpper bound for the time window, ISO 8601.
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.
include_videosNoReturn video URLs found on each result page.
exclude_domainsNoDrop results from these domains. Max 150, each ≤30 chars.
include_domainsNoOnly return results from these domains (e.g. 'arxiv.org'). Max 1000, each ≤30 chars.
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently notes that `full_content` is 'heavier — costs more context' and that `time_range` is mutually exclusive with `start_time`/`end_time`. However, it does not discuss failure modes, rate limits, or authentication requirements.

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 a single paragraph but well-structured, starting with the core purpose and then layering options. Every sentence adds value, and there is no fluff. It is appropriate in length for a tool with 18 parameters.

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?

Despite no output schema, the description covers return values (title, url, snippet) and mentions media URLs for `include_images`/`include_videos`. It addresses filtering, time windows, and content levels comprehensively. Minor omissions like pagination or error handling do not significantly detract from completeness.

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?

All 18 parameters have descriptions in the input schema (100% coverage), so the baseline is 3. The description adds significant value beyond schema descriptions by explaining purpose and usage nuances, such as 'heavier — costs more context' for `full_content` and 'mutually exclusive' for `time_range`, earning an above-baseline score.

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?

The description clearly states the tool's purpose: 'Search the live web with Octen and return ranked results (title, url, snippet).' It also differentiates from sibling tool 'news_search' by mentioning the `topic` parameter for news-focused results and from 'extract' by describing `full_content` as an optional heavier option.

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?

The description provides explicit guidance on when to use various features: set `topic` to 'news' for news results, use `highlight` for snippets, `full_content` for full page body with a warning about cost, and narrow with domain/text filters and time windows. It also implies when not to use `full_content` (only when snippet isn't enough) and mentions mutual exclusivity of `time_range` with absolute time parameters.

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/Octen-Team/octen-mcp'

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