Skip to main content
Glama
OmniExtract MCP

OmniExtract MCP

omni_extract_batch

Extract up to 10 URLs concurrently from X Articles, Douyin, TikTok, YouTube, GitHub, and web pages, converting each into clean Markdown for batch content processing.

Instructions

Concurrently extract up to 10 URLs (X Articles, Douyin, TikTok, YouTube, GitHub, Web) in parallel.

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": {
      "urls": "<urls>"
    },
    "name": "omni_extract_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesList of URLs to extract concurrently (max 10 per call).
api_keyNoOptional OmniExtract API key (omni_live_...).
include_transcriptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses concurrency and a maximum batch size, but omits authentication expectations, rate limits, partial-failure behavior, and whether extraction is read-only.

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?

A single front-loaded sentence with no filler. The platform list is parenthetical and does not obscure the core action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a batch extraction tool with no annotations and no output schema, the description is too sparse. It does not explain return shape, partial failures, authentication, or the effect of include_transcript, leaving the agent with significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents all three parameters, including the max-10 constraint and the optional api_key and include_transcript fields. The description mostly restates the schema's batch limit and does not clarify api_key or include_transcript semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('extract'), resource ('URLs'), and scope ('batch, up to 10, concurrently') and lists supported platforms. It is clear this is the batch variant, though it does not explicitly contrast with the sibling omni_extract_url.

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

Usage Guidelines2/5

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

It states the capability but gives no explicit guidance on when to use this tool versus omni_extract_url or when not to use it. The 'batch' and 'up to 10 URLs' wording only implies the use case.

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