Skip to main content
Glama

Keenable Web Search

This connector has been deprecated

search_web_pages

Read-onlyIdempotent

Search the live web with Keenable, a search engine built for AI agents. Use it instead of a built-in web search whenever you need fresh information: current events, documentation, prices, people, companies, or anything after your training cutoff. Answers in well under a second.

Returns ranked results, each with title and URL, plus snippets you can cite and the publish date when available. Snippets usually answer the question; to read a page, use fetch_page_content.

Example: {"query": "release notes for the latest Node.js LTS version", "published_after": "30d"}

Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue".

Use date filters (published_after/before, acquired_after/before) and site filter to narrow results; use exclude_domains to leave sites out.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_web_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoRestrict results to a specific site (e.g. "techcrunch.com")
queryYesNatural language search query. Should be a semantically rich description of the ideal page, not just keywords.
objectiveNoOptional. Two or three natural sentences, with no field labels and no line breaks, that cover: the exact facts, entities, numbers, dates or names a useful page must contain; task context the query does not state (who, where, when, eligibility, date window); which kinds of sources count or must be excluded; what is already established from earlier steps; and what is still unknown. Every sentence must be self-contained: name the entities, places, dates and figures explicitly, and never refer to 'the task', 'the clue', 'the question', 'above' or earlier results. Do not paste the conversation, and do not include personal, confidential or sensitive information. At most 1,000 characters.
query_timeNoLeave empty for a normal search. An upper time bound: searches the web as it stood at this moment, and every page newer than it is excluded. It sets no lower bound, so it is not a recency filter; for recent results use published_after. Accepts an ISO 8601 datetime (e.g. "2026-09-20T00:00:00Z"), a YYYY-MM-DD date, a Unix epoch, or an offset back from now ("7d" means as of 7 days ago, not the last 7 days)
session_idNoId of the agent session making this call. Send the same value on every call in one session so its requests can be grouped.
max_resultsNoHow many results to return. Ask for more when surveying a topic broadly, fewer for a quick lookup. When omitted, 10 results are returned.
disable_cardsNoReturn search results without cards.
output_formatNoResponse format: 'text' for readable text, or 'json' for the raw response serialized as JSON when you need to parse fields programmatically.text
acquired_afterNoKeep only pages Keenable acquired (indexed) after this point. Accepts a date (YYYY-MM-DD), an ISO 8601 timestamp, or a relative offset back from the request time such as "30min", "2h", "7d", "1mo" or "1y".
acquired_beforeNoKeep only pages Keenable acquired (indexed) before this point. Accepts a date (YYYY-MM-DD), an ISO 8601 timestamp, or a relative offset back from the request time such as "30min", "2h", "7d", "1mo" or "1y".
exclude_domainsNoNever return results from these sites. Entries are host names such as "example.com", which also covers its subdomains; up to 1,000 hosts. No paths or wildcards. A public suffix written with a leading dot, such as ".gov", excludes every host under it. A scheme, a leading "www." or a trailing "/" is cleaned up for you.
published_afterNoKeep only pages published after this point, a lower bound on publish time. Use this, not query_time, to get recent results: "7d" keeps the last 7 days. Accepts a date (YYYY-MM-DD), an ISO 8601 timestamp, or a relative offset back from the request time such as "30min", "2h", "7d", "1mo" or "1y".
published_beforeNoKeep only pages published before this point. Accepts a date (YYYY-MM-DD), an ISO 8601 timestamp, or a relative offset back from the request time such as "30min", "2h", "7d", "1mo" or "1y".
snippet_max_lengthNoHow many characters of snippet text to return for each result. Raise it when you need more context per result without fetching the page; lower it to keep the response short. When omitted, a default length is used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / max_results / maximum
      Previous value: -100New value: +50
  2. Changed1 schema field changed
    • changedInput schema / properties / max_results / maximum
      Previous value: -50New value: +100
  3. Changed2 schema fields changed
    • changedInput schema / properties / exclude_domains / description
      Previous value: -"Never return results from these sites. Entries are host names such as \"example.com\", which also covers its subdomains; up to 1,000 hosts. No paths, suffixes such as \".gov\", or wildcards. A scheme, a leading \"www.\" or a trailing \"/\" is cleaned up for you."New value: +"Never return results from these sites. Entries are host names such as \"example.com\", which also covers its subdomains; up to 1,000 hosts. No paths or wildcards. A public suffix written with a leading dot, such as \".gov\", excludes every host under it. A scheme, a leading \"www.\" or a trailing \"/\" is cleaned up for you."
    • addedInput schema / properties / objective
      Added value: +{
      +  "description": "Optional. Two or three natural sentences, with no field labels and no line breaks, that cover: the exact facts, entities, numbers, dates or names a useful page must contain; task context the query does not state (who, where, when, eligibility, date window); which kinds of sources count or must be excluded; what is already established from earlier steps; and what is still unknown. Every sentence must be self-contained: name the entities, places, dates and figures explicitly, and never refer to 'the task', 'the clue', 'the question', 'above' or earlier results. Do not paste the conversation, and do not include personal, confidential or sensitive information. At most 1,000 characters.",
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / exclude_domains
      Added value: +{
      +  "description": "Never return results from these sites. Entries are host names such as \"example.com\", which also covers its subdomains; up to 1,000 hosts. No paths, suffixes such as \".gov\", or wildcards. A scheme, a leading \"www.\" or a trailing \"/\" is cleaned up for you.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  5. Changed1 schema field changed
    • removedInput schema / properties / mode
      Removed value: -{
      -  "description": "Search mode: 'pro' (default) for enhanced results or 'realtime' for fastest results",
      -  "enum": [
      -    "realtime",
      -    "pro"
      -  ],
      -  "type": "string"
      -}
  6. Changed8 schema fields changed
    • changedInput schema / properties / acquired_after / description
      Previous value: -"Filter results to pages acquired/indexed after this date (YYYY-MM-DD)"New value: +"Keep only pages Keenable acquired (indexed) after this point. Accepts a date (YYYY-MM-DD), an ISO 8601 timestamp, or a relative offset back from the request time such as \"30min\", \"2h\", \"7d\", \"1mo\" or \"1y\"."
    • changedInput schema / properties / acquired_before / description
      Previous value: -"Filter results to pages acquired/indexed before this date (YYYY-MM-DD)"New value: +"Keep only pages Keenable acquired (indexed) before this point. Accepts a date (YYYY-MM-DD), an ISO 8601 timestamp, or a relative offset back from the request time such as \"30min\", \"2h\", \"7d\", \"1mo\" or \"1y\"."
    • changedInput schema / properties / max_results / description
      Previous value: -"Maximum number of results to return. When omitted, a default count (10) is used."New value: +"How many results to return. Ask for more when surveying a topic broadly, fewer for a quick lookup. When omitted, 10 results are returned."
    • changedInput schema / properties / output_format / description
      Previous value: -"Response format: 'text' (default) for readable text, or 'json' for the raw response serialized as JSON."New value: +"Response format: 'text' for readable text, or 'json' for the raw response serialized as JSON when you need to parse fields programmatically."
    • changedInput schema / properties / published_after / description
      Previous value: -"Filter results to pages published after this date (YYYY-MM-DD), a lower bound on publish time. Use this, not query_time, to get recent results."New value: +"Keep only pages published after this point, a lower bound on publish time. Use this, not query_time, to get recent results: \"7d\" keeps the last 7 days. Accepts a date (YYYY-MM-DD), an ISO 8601 timestamp, or a relative offset back from the request time such as \"30min\", \"2h\", \"7d\", \"1mo\" or \"1y\"."
    • changedInput schema / properties / published_before / description
      Previous value: -"Filter results to pages published before this date (YYYY-MM-DD)"New value: +"Keep only pages published before this point. Accepts a date (YYYY-MM-DD), an ISO 8601 timestamp, or a relative offset back from the request time such as \"30min\", \"2h\", \"7d\", \"1mo\" or \"1y\"."
    • changedInput schema / properties / session_id / description
      Previous value: -"Optional id of the agent session making this call. Send the same value on every call in one session so its requests can be grouped."New value: +"Id of the agent session making this call. Send the same value on every call in one session so its requests can be grouped."
    • changedInput schema / properties / snippet_max_length / description
      Previous value: -"Maximum length (characters) of the snippet returned per result. When omitted, a default length is used."New value: +"How many characters of snippet text to return for each result. Raise it when you need more context per result without fetching the page; lower it to keep the response short. When omitted, a default length is used."
  7. Changed2 schema fields changed
    • addedInput schema / properties / disable_cards
      Added value: +{
      +  "default": false,
      +  "description": "Return search results without cards.",
      +  "type": "boolean"
      +}
    • removedInput schema / properties / enable_wizards
      Removed value: -{
      -  "default": false,
      -  "description": "Experimental: use wizards (structured data outputs). Only valid in 'pro' mode, and not under a zero data retention policy.",
      -  "type": "boolean"
      -}
  8. Changed1 schema field changed
    • changedInput schema / properties / enable_wizards / description
      Previous value: -"Experimental: use wizards (structured data outputs). Only valid in 'pro' mode."New value: +"Experimental: use wizards (structured data outputs). Only valid in 'pro' mode, and not under a zero data retention policy."
  9. Changed2 schema fields changed
    • removedInput schema / properties / enableWizards
      Removed value: -{
      -  "default": false,
      -  "description": "Experimental: use wizards (structured data outputs). Only valid in 'pro' mode.",
      -  "type": "boolean"
      -}
    • addedInput schema / properties / enable_wizards
      Added value: +{
      +  "default": false,
      +  "description": "Experimental: use wizards (structured data outputs). Only valid in 'pro' mode.",
      +  "type": "boolean"
      +}
  10. Changed2 schema fields changed
    • changedInput schema / properties / published_after / description
      Previous value: -"Filter results to pages published after this date (YYYY-MM-DD)"New value: +"Filter results to pages published after this date (YYYY-MM-DD), a lower bound on publish time. Use this, not query_time, to get recent results."
    • changedInput schema / properties / query_time / description
      Previous value: -"Point-in-time search: exclude pages newer than this timestamp. Accepts an ISO 8601 datetime (e.g. \"2026-09-20T00:00:00Z\"), a YYYY-MM-DD date, a Unix epoch, or a relative offset back from now (e.g. \"7d\", \"2w\", \"30min\")"New value: +"Leave empty for a normal search. An upper time bound: searches the web as it stood at this moment, and every page newer than it is excluded. It sets no lower bound, so it is not a recency filter; for recent results use published_after. Accepts an ISO 8601 datetime (e.g. \"2026-09-20T00:00:00Z\"), a YYYY-MM-DD date, a Unix epoch, or an offset back from now (\"7d\" means as of 7 days ago, not the last 7 days)"
  11. Changed1 schema field changed
    • addedInput schema / properties / output_format
      Added value: +{
      +  "default": "text",
      +  "description": "Response format: 'text' (default) for readable text, or 'json' for the raw response serialized as JSON.",
      +  "enum": [
      +    "text",
      +    "json"
      +  ],
      +  "type": "string"
      +}
  12. Changed1 schema field changed
    • addedInput schema / properties / enableWizards
      Added value: +{
      +  "default": false,
      +  "description": "Experimental: use wizards (structured data outputs). Only valid in 'pro' mode.",
      +  "type": "boolean"
      +}
  13. Changed1 schema field changed
    • changedInput schema / properties / query_time / description
      Previous value: -"Point-in-time search: exclude pages newer than this timestamp. ISO 8601 datetime or relative (e.g. \"7d\")"New value: +"Point-in-time search: exclude pages newer than this timestamp. Accepts an ISO 8601 datetime (e.g. \"2026-09-20T00:00:00Z\"), a YYYY-MM-DD date, a Unix epoch, or a relative offset back from now (e.g. \"7d\", \"2w\", \"30min\")"
  14. Changed1 schema field changed
    • addedInput schema / properties / session_id
      Added value: +{
      +  "description": "Optional id of the agent session making this call. Send the same value on every call in one session so its requests can be grouped.",
      +  "maxLength": 128,
      +  "type": "string"
      +}
  15. Changed2 schema fields changed
    • changedInput schema / properties / mode / description
      Previous value: -"Search mode: 'pro' (default) for enhanced results"New value: +"Search mode: 'pro' (default) for enhanced results or 'realtime' for fastest results"
    • changedInput schema / properties / mode / enum
      Previous value: -[
      -  "pro"
      -]New value: +[
      +  "realtime",
      +  "pro"
      +]
  16. Changed1 schema field changed
    • addedInput schema / properties / max_results
      Added value: +{
      +  "description": "Maximum number of results to return. When omitted, a default count (10) is used.",
      +  "maximum": 50,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  17. Changed1 schema field changed
    • addedInput schema / properties / query_time
      Added value: +{
      +  "description": "Point-in-time search: exclude pages newer than this timestamp. ISO 8601 datetime or relative (e.g. \"7d\")",
      +  "type": "string"
      +}
  18. Changed1 schema field changed
    • addedInput schema / properties / snippet_max_length
      Added value: +{
      +  "description": "Maximum length (characters) of the snippet returned per result. When omitted, a default length is used.",
      +  "maximum": 10000,
      +  "minimum": 180,
      +  "type": "integer"
      +}
  19. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is free. The description adds real context beyond that: sub-second latency, the exact returned fields (title, URL, citable snippets, publish date), and the important behavioral caveat that snippets often suffice before paying for a page fetch. Minor gap: the cards concept behind disable_cards is never explained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and the sibling handoff, then returns, then an example, then query tips, then filter guidance. Every sentence carries distinct information and the length is proportionate to a 14-parameter tool. No filler or repetition of the schema verbatim.

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?

With 14 parameters and no output schema, the description correctly compensates by describing the return shape (ranked results, title, URL, snippets, publish date) and by clarifying the trap-prone query_time versus published_after distinction. It falls just short of complete because card behavior and pagination/breadth limits are not addressed in prose.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema carries the per-field burden and baseline would be 3. The description earns above baseline by teaching query construction ("describe the ideal page, not keywords" with a concrete contrasting pair), supplying a worked example combining query with published_after, and grouping the date/site filters by purpose.

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 specific verb and resource ("Search the live web") plus the concrete engine identity and audience ("a search engine built for AI agents"). It explicitly separates itself from a built-in web search and from the read-a-page sibling fetch_page_content, so an agent can route correctly 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?

Gives explicit when-to-use triggers (current events, documentation, prices, people, companies, anything after the training cutoff) and an explicit handoff condition: "Snippets usually answer the question; to read a page, use fetch_page_content." The closing paragraph adds filter-selection guidance (date filters and site filter to narrow, exclude_domains to leave sites out).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.