Skip to main content
Glama
Sign In
Heym

Heym

Official
by heymrun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

website_loader

Loads and extracts text content from any web URL using Jina. Returns structured, readable text from web pages.

Instructions

loads any given web url using Jina

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": "website_loader"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesInput field: url

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.0.31
  2. Removed
  3. Addedv0.0.30

TDQS

B3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'loads' using Jina, but does not explain what 'loading' entails (e.g., fetching text, images, or entire page), potential side effects, or any limitations. This is insufficient for safe tool invocation.

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

Conciseness3/5

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

The description is very concise, consisting of a single sentence. However, it could be more structured to include key information such as output behavior or usage tips. It is not overly verbose, but lacks the depth that would make it highly effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has one parameter, no annotations, and no output schema, the description is inadequate. It provides no information about return values, error handling, or any behavioral specifics beyond a vague 'loads'. For a web loading tool, more context is needed.

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?

The input schema has one parameter 'url' with description 'Input field: url'. The tool description adds no additional semantic information beyond the schema. Since schema description coverage is 100%, the baseline is 3, and the description does not enhance understanding of the parameter's format or constraints.

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?

The description uses a specific verb 'loads' and identifies the resource as 'any given web url', clearly stating the action and object. It also mentions 'using Jina', adding context. The sibling tool 'calculator' is completely different, so there is no confusion.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, no mention of when not to use it, and no explanation of prerequisites or context. The description simply states what the tool does without any usage recommendations.

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

Deploy Server

Other Tools