Skip to main content
Glama
Sign In

Keenable Web Search

by ai.keenable.api
OverviewDiscussionsAdmin

fetch_page_content

Read-onlyIdempotent

Fetch and extract content from a web page. Returns the page content in markdown format.

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_charsNoCharacter 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.
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. 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."
  2. 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"
+}
  3. 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"
+}
  4. 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"
+}
  5. Changed1 schema field changed
    • addedInput schema / properties / live
      Added value: +{
+  "default": false,
+  "description": "Fetch live content. Defaults to false.",
+  "type": "boolean"
+}
  6. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds the return format (markdown), which is genuinely useful beyond the annotations, but it omits the 50000-character default truncation and the indexed-vs-live fallback behavior—both of which materially affect what the agent gets back.

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?

Two short sentences, front-loaded with the action and followed by the output format. Nothing is redundant and nothing is buried.

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 rich annotations, a fully documented six-parameter schema, and no output schema, the description covers the essentials: what it does and what it returns. It falls just short of complete because it never mentions the indexing/live distinction or prompt-based extraction, which are the tool's most consequential behaviors.

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%: url, live, prompt, max_chars, session_id, and output_format each carry detailed, example-backed descriptions. The description adds no parameter meaning beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Fetch and extract content from a web page") plus the return format (markdown), so an agent knows exactly what the tool produces. It does not distinguish itself from the sibling search_web_pages, so the agent must infer that this one requires a known URL while the sibling discovers URLs.

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

Usage Guidelines3/5

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

Usage is only implied: "Fetch and extract content from a web page" suggests it is for when you already have a URL, but the description never says when to prefer this over search_web_pages or when live/indexed fetching applies. Those selection rules exist only in the schema parameter descriptions, not in the description itself.

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

All Keenable Web Search toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources