Skip to main content
Glama
aashuchahal4-crypto

creatoros-mcp

by aashuchahal4-crypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

creatoros_search

Search the live web and extract Markdown content from top-ranked result pages in one step, giving AI agents current information and source snippets for queries without a target URL.

Instructions

Executes an autonomous live web search for fresh information and automatically extracts deep Markdown content from the highest-ranking search result pages. Combines web search retrieval and web scraping in a single step for AI agents.

When to use:

  • Use when you need real-time, up-to-date web information, breaking news, latest documentation, or answers to queries where no specific target URL is provided.

When NOT to use:

  • If the user has already provided an exact web URL to scrape, use creatoros_extract instead.

Behavior:

  • Read-only and non-destructive.

  • Returns a structured Markdown document containing top ranked titles, URLs, text snippets, and extracted page content.

Input Schema

NameRequiredDescriptionDefault
limitNoThe maximum number of top search results to return and extract (integer between 1 and 5). Default is 5.
queryYesThe search query keywords or question to look up on the live web (e.g. "Python 3.13 release changelog features", "FastAPI production best practices").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.0.1
    • addedInput schema / properties / limit / default
      Added value: +5
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of search results to return (1 to 5). Default is 5."New value: +"The maximum number of top search results to return and extract (integer between 1 and 5). Default is 5."
    • addedInput schema / properties / limit / maximum
      Added value: +5
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / query / description
      Previous value: -"The search query to look up (e.g. \"latest Python 3.13 release notes\", \"FastAPI RAG tutorial\")."New value: +"The search query keywords or question to look up on the live web (e.g. \"Python 3.13 release changelog features\", \"FastAPI production best practices\")."
    • addedInput schema / properties / query / maxLength
      Added value: +250
    • addedInput schema / properties / query / minLength
      Added value: +2
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does declare read-only/non-destructive semantics plus the return shape (titles, URLs, snippets, extracted page content). It omits operational traits like latency/cost of scraping up to five pages, rate limits, or what happens when extraction fails on a page.

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 the core action, then cleanly sectioned into When to use / When NOT to use / Behavior. Slight redundancy in restating that it combines search and scraping 'in a single step', but overall tight and scannable.

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?

There is no output schema, and the description compensates by enumerating the returned Markdown document contents. For a simple two-parameter retrieval tool this is nearly sufficient; only failure modes and cost/time expectations are left unaddressed.

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 both parameters are already documented with bounds, defaults, and examples, making 3 the baseline. The description adds only that results are 'highest-ranking' and top-ranked; it says nothing about the trade-off of increasing limit (more pages scraped, slower/heavier).

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 concrete verb+resource pair: performs a live web search and extracts Markdown from top-ranking result pages. It also distinguishes itself from the sibling scraping tool, so an agent can tell the two apart without opening either 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?

Provides an explicit 'When to use' (real-time info, breaking news, latest docs, no target URL given) and 'When NOT to use' that names creatoros_extract as the alternative for exact URLs. Clear positive and negative routing conditions.

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