Skip to main content
Glama
Octen-Team

octen-mcp

Official
by Octen-Team

search

Run a single web query and get ranked results with title, URL, and snippet. Filter by language, news topic, time window, or domain; request per-result highlights or full page content.

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 / include_videos to return media 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.
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). 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.
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?

No annotations are provided, so the description carries the full burden. It discloses the real-time freshness ('fast, fresh, real-time'), the cost tradeoff of full_content ('heavier — costs more context'), and the mutual exclusivity of time_range vs start_time/end_time. It could add rate-limit or ranking detail, but for a read-style search tool it is substantially transparent.

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?

Well structured and front-loaded: first paragraph states core function plus key options, second paragraph gives usage guidance, and the final keywords line aids discoverability. Slightly long but every section earns its place; no waste or repetition.

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?

For a 19-parameter tool with nested objects and no output schema, the description is appropriately complete. It covers the primary capability, key optional features (highlight/full_content, media, filters, time windows), return shape ('title, url, snippet'), and guidance on alternatives—adequate for an agent to decide when and how to invoke.

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 baseline is 3. The description adds framing—distinguishing highlight ('ranked snippet') from full_content ('cleaned page body... heavier') and hinting at filter groupings—but does not materially go beyond the already-rich schema descriptions for individual parameters.

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?

Description opens with a specific verb+resource: 'Search the live web and return ranked results (title, url, snippet)' and explicitly scopes it to 'one focused lookup.' It clearly distinguishes from siblings by naming broad_search and extract as alternatives for other use cases, and offers distinct purpose-laden parameters (highlight, full_content, topic=news).

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 USE FOR guidance states when to use ('a single focused lookup: one fact, one entity, one document'), when not to ('If the question spans several independent subtopics... use broad_search instead'), and names concrete alternatives (broad_search, extract). Also warns that a sequence of search calls 'is slower and gives worse coverage than one fan-out.'

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