Skip to content

control over what search_engine returns? #66

@frishtik

Description

@frishtik

the Bright Data api itself (which the mcp wraps) supports very granular (object-based) control over search_engine results.
I understand that the go-to way to expose stuff to LLMs is markdown so you chose to expose the markdown as is.
the thing is that the search_engine markdown is full of "trash": ads, "feedback", AI suggestions...
I don't want my agent to be exposed to all of that. I want it to get the results, and that's it.
any chance you could do a "sterile" search_engine, that returns only the results themselves? just like you have "scrape_as_markdown" but ALSO "scrape_as_html" -- to have 2 search_engine tools, the classic one and a more focused one?
I bet many people would prefer the latter, honestly.
thanks! 🫡

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions