Skip to main content
Glama

Keenable Web Search

This connector has been deprecated

fetch_page_content

Read-onlyIdempotent

Read any web page with Keenable. Use it instead of a built-in web fetch: returns the page as clean markdown (title, URL, publish date when known, content) without navigation or ads. Add a prompt to get back only the part you need from a long page.

Example: {"url": "https://nodejs.org/en/about/previous-releases", "prompt": "Which version is the current LTS?"}

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": {
      "url": "<url>"
    },
    "name": "fetch_page_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to fetch. Example: "https://example.com"
liveNoFetch the page live from the source instead of returning Keenable's indexed copy. Use it for pages that change often or URLs that are not indexed.
promptNoExtraction instruction for this page. When set, an LLM reads the fetched page and the returned content is only the output for this instruction instead of the full page; use it when you need one detail from a long page. Example: "List all pricing tiers with their monthly prices".
max_charsNoHard cap on the characters of returned page content. Longer pages are cut to fit, ending with "..." unless max_chars is 3 or less, and the output says how long the full page is. Lower it to save context on long pages. When omitted, up to 20000 characters are returned.
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.
output_formatNoResponse format: 'text' for readable text, or 'json' for the raw response serialized as JSON when you need to parse fields programmatically.text

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / max_chars / description
      Previous value: -"Hard cap on the characters of returned page content. Longer pages are cut to fit, ending with \"...\" unless max_chars is 3 or less, and the output says how long the full page is. Lower it to save context on long pages. When omitted, up to 50000 characters are returned."New value: +"Hard cap on the characters of returned page content. Longer pages are cut to fit, ending with \"...\" unless max_chars is 3 or less, and the output says how long the full page is. Lower it to save context on long pages. When omitted, up to 20000 characters are returned."
  2. Changed1 schema field changed
    • changedInput schema / properties / max_chars / description
      Previous value: -"Character budget for the returned page content; anything beyond it is cut off. Lower it to save context on long pages. When omitted, up to 50000 characters are returned."New value: +"Hard cap on the characters of returned page content. Longer pages are cut to fit, ending with \"...\" unless max_chars is 3 or less, and the output says how long the full page is. Lower it to save context on long pages. When omitted, up to 50000 characters are returned."
  3. Changed5 schema fields changed
    • changedInput schema / properties / live / description
      Previous value: -"Fetch live content. Defaults to false."New value: +"Fetch the page live from the source instead of returning Keenable's indexed copy. Use it for pages that change often or URLs that are not indexed."
    • changedInput schema / properties / max_chars / description
      Previous value: -"Maximum number of characters of content to return. Longer content is truncated. Defaults to 50000 when omitted."New value: +"Character budget for the returned page content; anything beyond it is cut off. Lower it to save context on long pages. When omitted, up to 50000 characters 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 / prompt / description
      Previous value: -"Optional extraction instruction. When set, an LLM reads the fetched page and the returned content is only the output for this instruction instead of the full page. Example: \"List all pricing tiers with their monthly prices\"."New value: +"Extraction instruction for this page. When set, an LLM reads the fetched page and the returned content is only the output for this instruction instead of the full page; use it when you need one detail from a long page. Example: \"List all pricing tiers with their monthly prices\"."
    • 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."
  4. 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"
      +}
  5. 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"
      +}
  6. Changed1 schema field changed
    • addedInput schema / properties / prompt
      Added value: +{
      +  "description": "Optional extraction instruction. When set, an LLM reads the fetched page and the returned content is only the output for this instruction instead of the full page. Example: \"List all pricing tiers with their monthly prices\".",
      +  "maxLength": 2000,
      +  "type": "string"
      +}
  7. Changed1 schema field changed
    • addedInput schema / properties / live
      Added value: +{
      +  "default": false,
      +  "description": "Fetch live content. Defaults to false.",
      +  "type": "boolean"
      +}
  8. First observed

TDQS

A4.1/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 covered. The description adds value beyond that by describing the response payload and its cleaned-up nature (no navigation or ads) and by explaining that a prompt triggers an LLM extraction pass rather than a raw page return.

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

Conciseness4/5

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

The text is front-loaded with purpose, then differentiation, then the extraction tip, with no filler sentences. The worked example is useful but partially restates the prompt guidance already given in prose, so it is slightly longer than strictly necessary.

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?

For a six-parameter tool with no output schema, the description covers what comes back and how prompt mode changes it, which is the critical gap it needed to fill. It leaves out failure behavior (unreachable pages, unindexed URLs without live=true) and any auth or rate-limit context.

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

Parameters3/5

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

Schema description coverage is 100%, and the schema already documents url, live, prompt, max_chars, session_id and output_format in detail. The description only reinforces the prompt parameter's intent (extract one detail from a long page), adding little beyond what the structured fields already say, so the baseline 3 applies.

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?

"Read any web page with Keenable" gives a specific verb and resource, then immediately specifies the return shape (title, URL, publish date, content as clean markdown). The contrast with a built-in web fetch and the read-vs-search distinction from search_web_pages make it identifiable without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes the agent away from a built-in fetch and gives a condition for the prompt mode ("when you need one detail from a long page"). It does not state when not to use it or contrast with the sibling search tool, so it stops short of full when/when-not coverage.

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.