- 2 minutes to read

ContentSearchMaxResults - System Parameter

New 7.12

ContentSearchMaxResults is an integer System Parameter that limits how many documents one search returns in Content Search: the Search content dialog for Articles, Snippets, Templates, and Document Profiles. The Web API reads it for every search, from the Web Client and from the AI assistant.

At a Glance

Property Value
Key ContentSearchMaxResults
Data type integer (documents per search)
Default 100
Read by Web API
Takes effect At the next search when saved on the System Parameters page; within about 15 seconds in other processes, such as the MCP Endpoint; no restart needed
Status ✅ Active
Since Nodinite 7.12

How It Works

  • The search finds every matching document, sorts them best match first, and keeps the first ContentSearchMaxResults. The result pages through those.
  • When the limit cuts the result, the line above the results shows an orange limited to N documents badge; its tooltip names this parameter.
  • The MCP tool search_content returns at most 50 documents per call, whatever this value; see MCP Tool Reference.

Search content results with the orange badge limited to 5 documents, after ContentSearchMaxResults was set to 5 (7.12)
With the value set to 5, the search stops at five documents and says so.

See Content Search - Limits for all three limits together.

System Parameters page filtered on ContentSearch, showing ContentSearchMaxMatchesPerDocument 10, ContentSearchMaxResults 100, and ContentSearchMaxScannedDocuments 2000 with their descriptions (7.12)
Filter on ContentSearch to see the three Content Search limits together; this page covers ContentSearchMaxResults.

Choosing a Value

Keep the default. When searches are often limited, narrow them first: tick fewer document types, search Titles only, or use Phrase or Whole word. Raise the value when your Repository is large and you need the full list; a larger value makes each search return more data.

Next Steps