max_results sets how many results come back, snippet_max_length caps the page text in each one, and disable_cards keeps every result an ordinary web page.
Parameters
A search costs the same whether it returns 1 result or 50. See Pricing.
Search with a fixed size and no cards
This sample asks for 3 results with snippets of at most 180 characters and no cards, then prints each URL with the length of its snippet. It runs with no API key:Example output · results vary
Cards and disable_cards
For queries such as prices, exchange rates or facts about a company, Keenable can write a result itself: a card. A card’surl starts with https://cards.keenable.ai/w/ and works for one day. This result is from the same request without disable_cards:
Response excerpt · results vary
disable_cards: true, an ordinary web page takes the card’s place, so you still get the same number of results. Send it when your code stores URLs, cites them after a day, or must cite the original publisher.
Pick the sizes
Start from the job, then tune with what your agent’s context can hold:
If you leave
snippet_max_length out, snippets can run to several thousand characters each, and 10 results come back. Set both on every search an agent makes.
Common mistakes
In the SDKs, CLI and MCP
Over MCP,
search_web_pages takes all three (see MCP server). To size the prompt block you build from the results, see Control context size.
API reference
- Search request:
max_results,snippet_max_lengthanddisable_cardsin full. - Search, then fetch: read snippets first and fetch only what they miss.
- Ground answers with citations: turn the results into a cited prompt.