Conversation
Adds tools/toolkits/search/serply.mdx and its docs.json nav entry. Params and functions are read off libs/agno/agno/tools/serply.py at the agno SHA this repo's CI pins. Companion to agno-agi/agno#9780.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This is the companion docs PR @kausmeows asked for when the SDK toolkit merged:
(agno-agi/agno#9780, 2026-08-26)
SerplyToolsshipped in that PR andexamples/tools/serply-tools.mdxalready exists here, but the toolkit reference page was never added. Serply is currently the only entry in the Tools > Search group without one; the other 22 all have atools/toolkits/search/<name>.mdx.Changes:
tools/toolkits/search/serply.mdx(new). Structured like its nearest siblingserper.mdx: Prerequisites, Example, Toolkit Params, Toolkit Functions, Developer Resources.docs.json(one line). Added to the Tools > Search group, alphabetically betweenserperandsofya.The param and function tables are read off
libs/agno/agno/tools/serply.pyat the agno SHA this repo's CI pins (9dd8f80), not written from memory. One behaviour is worth calling out because it differs from the neighbouring pages:search_newsandsearch_scholardefault toFalseonSerplyTools, whereSerperToolsdefaults everything on. The page shows the flag that turns them on instead of implying all three tools are live out of the box.No redirect entry was added. The
integrations/toolkits/search/*redirects are legacy path migrations, and the newest toolkits (seltz,scavio,sofya) have none. Serply never existed at the old path.Type of Change
Related Issues/PRs (if applicable)
Checklist
scripts/make_openapi.py --checkpasses (if applicable)mint broken-links -t falseandmint validate -t falsepassWhat was run
mint validate -t falsemint broken-links -t falsepython3 scripts/check_install_coverage.py --json --limit 0offender_pages0,missing_requirements_total0python3 scripts/check_imports.pypython3 scripts/reference_drift.pycheck_imports.pyresolvingfrom agno.tools.serply import SerplyToolsis the one that matters here, and it does: bothlibs/agno/agno/tools/serply.pyandcookbook/91_tools/serply_tools.pyexist at the pinned SHA.Two boxes left unticked on purpose rather than guessed at:
scripts/make_openapi.py --checkhas nothing to say about this diff.scripts/examples_sync/*. I did not run the sync chain. It regeneratesexamples/**andmerge_nav.pyoperates only on the Examples tab ofdocs.json; this PR adds a page undertools/toolkits/search/and touches the Tools tab, so the chain has no input from it and thegit diff --exit-codethat follows it should stay clean. Flagging it so a maintainer can confirm rather than take my word for it.Disclosure
I work on Serply. The page documents the toolkit as it is implemented in agno today and adds no vendor claims. The Developer Resources link to serply.io/docs mirrors what
valyu.mdxandparallel.mdxalready do for their own APIs. Happy to drop it if you would rather the page stayed link-free.