Skip to main content
Glama
octen-mcp

octen-mcp

Official
by Octen-Team

Web Search

search
Read-only

Perform real-time web lookups for a single focused query and return ranked titles, URLs, and snippets, with domain, language, and time filters.

Instructions

Search the live web and return ranked results (title, url, snippet) — fast, fresh, real-time web search for one focused lookup. For news use news_search; for anything about a company or the people in one — what it does, who runs it, its revenue or share price, what it has announced — use business_search; when all you need is the URL of a site or docs page you could almost name, use pulse_search. 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 that needs real retrieval and is not already covered by a tool above: one fact, one page, one document you do not already know the address of. 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

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
countNoNumber of results to return (1-100). Default 5.
queryYesNon-empty search query. Max 500 chars.
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. Changed1 schema field changedv0.7.1
    • removedInput schema / properties / topic
      Removed value: -{
      -  "default": "general",
      -  "description": "Search category: `general` for broad web search, `news` for news-focused results. Default general.",
      -  "enum": [
      -    "general",
      -    "news"
      -  ],
      -  "type": "string"
      -}
  2. 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
  3. 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"
      -}
  4. 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."
  5. Addedv0.3.6
  6. Removedv0.3.5
  7. Addedv0.3.4
  8. Removedv0.3.3
  9. Addedv0.2.2

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint=false, so the safety profile is covered by structured data. The description adds genuinely new behavioral context: full_content is 'heavier — costs more context' versus highlight, and results are 'fast, fresh, real-time'. It does not mention rate limits, result freshness caveats, or failure behavior, keeping it short of a 5.

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?

Front-loaded with purpose and return shape, then alternatives, then capability summary, then a one-line scope rule. Most sentences carry routing or cost information. The trailing 'keywords' line is somewhat redundant with the opening verb phrases, though it aids retrieval matching.

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 17-parameter tool with nested objects and no output schema, the description covers the return shape (title/url/snippet plus optional highlights, full page body, image URLs) and the key parameter interactions an agent must get right. The remaining unmentioned parameters (count, format, safesearch, timeout) are fully documented in the schema, so the gap is minor.

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 description coverage is 100%, so the baseline is 3 and the schema does most of the work. The description nonetheless adds cross-parameter meaning beyond the schema fields: the highlight-vs-full_content cost tradeoff, grouped framing of domain/text include-exclude filters, the published/crawled time basis, and relative time_range as an alternative to absolute start/end. It omits count, format, safesearch, and timeout, which the schema already covers.

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+return shape ('Search the live web and return ranked results (title, url, snippet)') and immediately enumerates the sibling tools it is not, with the condition that selects each. An agent can distinguish this from news_search, business_search, pulse_search, broad_search, and extract 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 explicit routing rules in both directions: 'For news use news_search', 'anything about a company... use business_search', 'URL of a site or docs page... use pulse_search', 'if the question spans several independent subtopics... use broad_search instead', 'to read a page you already have the URL for, use extract'. It also states a negative condition ('not already covered by a tool above') and scopes to 'one focused lookup'.

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