Skip to main content
Glama
Octen-Team

octen-mcp

Official
by Octen-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

News Search

news_search
Read-only

Search recent news and return ranked articles (title, URL, snippet) for current events, headlines, and timely reporting.

Instructions

Search recent news and return ranked articles (title, url, snippet) — current events, headlines, timely reporting. This is search locked to topic: news; same options as search (domain / text filters, language filter, time window, highlight / full_content, media) except topic, which is fixed to news.

For a single news lookup this is the right tool. For a multi-angle news question ("what shipped across the industry this month", "how are different outlets covering X"), use broad_search with topic=news instead of looping news_search.

keywords: news search, latest news, headlines, current events, breaking news, recent, today, this week, press coverage

Input Schema

TableJSON 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. 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. Changed1 schema field changedv0.3.4
    • removedInput schema / properties / country
      Removed value: -{
-  "default": "auto",
-  "description": "Follow ISO 3166, the International Standard for country codes and codes for their subdivisions (e.g. `US`, `JP`); `auto` (default) determines it automatically.",
-  "type": "string"
-}
  7. Changed1 schema field changedv0.3.3
    • addedInput schema / properties / country
      Added value: +{
+  "default": "auto",
+  "description": "Follow ISO 3166, the International Standard for country codes and codes for their subdivisions (e.g. `US`, `JP`); `auto` (default) determines it automatically.",
+  "type": "string"
+}
  8. Addedv0.2.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false), so the bar is lower. The description adds real context beyond them: ranked results with a defined field set, and that this is `search` with topic fixed and all other options identical. It doesn't mention rate limits, result freshness lag, or pagination, which keeps it out of 5 territory.

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 routing, then scope constraint. Content is dense and earns its place, though the trailing 'keywords:' line is largely redundant term-stuffing that a capable agent doesn't need for selection.

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 no output schema, the description supplies the return field set and the inherited-option contract from `search`, which is the key missing piece. Remaining gaps (pagination, cost of highlight vs full_content beyond the schema's own note) are minor since the schema is fully annotated.

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 every parameter is already documented in the schema, including defaults, ranges, and enums. The description summarizes option groups (domain/text filters, language, time window, highlight/full_content, media) and clarifies topic is not settable, which is mild added value but no per-parameter syntax or interaction details beyond the schema.

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+resource (search news, return ranked articles) and pins down what it actually is: `search` locked to `topic: news`. It also names the return fields (title, url, snippet), so an agent can distinguish it from `search`, `image_search`, and `video_search` without opening schemas.

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?

Explicitly routes: single news lookup -> this tool; multi-angle news questions -> `broad_search` with topic=news, with two concrete example queries and an explicit warning against looping news_search. This is the when/when-not/alternative pattern done well.

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