Skip to main content
Glama
Octen-Team

octen-mcp

Official
by Octen-Team

extract

Fetch multiple URLs and return LLM-ready content. Use an optional query to get the most relevant highlights instead of full text. Every result includes category and page structure classification.

Instructions

Fetch one or more URLs and return LLM-ready content from Octen. Unique to Octen: pass a query to get the most relevant highlights per page instead of the full body; every result includes a category (topical) and page_structure (typology) classification. Bare hosts like 'octen.ai' are auto-normalized to https. Cached when fresh.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsYesURLs to extract. 1-20 per call. Bare hosts ok.
queryNoOptional intent-focused keywords. When set, each result returns `highlights` (most relevant snippets, ranked) instead of `full_content`.
max_age_secondsNoMaximum age of cached content in seconds. Default 24h. Lower this for time-sensitive pages (news / prices).
formatNoOutput format. Default markdown.markdown
timeoutNoPer-URL timeout in seconds (1-60).
include_imagesNoReturn image URLs found on each page.
include_videosNoReturn video URLs found on each page.
include_audioNoReturn audio URLs found on each page.
include_faviconNoReturn each page's favicon URL.
Behavior4/5

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

In the absence of annotations, the description discloses key behaviors: auto-normalization of bare hosts to https, caching policy, and query behavior switching output from full content to highlights. It does not cover error handling or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three concise sentences that front-load the core function, then explain unique features and caching. Every sentence adds value without redundancy.

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?

The description mentions return content types (highlights, full content) and classifications (category, page_structure) but lacks explicit details on the response structure. Given the 9 parameters and no output schema, it is mostly complete but could specify exact fields.

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 parameters are well-documented in the schema. The description adds marginal value by explaining the overall purpose and query behavior, but does not deeply elaborate on each parameter beyond what the schema provides.

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 fetches URLs and returns LLM-ready content, highlighting unique features like query-based highlights and classifications, which distinguishes it from simple fetch tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While the description notes caching and normalization behaviors, it does not explicitly guide when to use this tool over alternatives or when not to use it. With no sibling tools, the context is limited.

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