John's Essentials

analyze_link_extractor

Read-only

Link Extractor — Extract all hyperlinks from a PDF or HTML file, or from pasted text. Other file types are scanned as raw text. [category: analyze]

Input Schema

TableJSON Schema

Name	Required	Description	Default
`file`	No	A PDF or HTML file to pull the links out of. Any other type is read as plain text.
`text`	No	Paste text or HTML to pull links out of. Ignored if a file is attached — the file wins.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026
- addedInput schema / properties / text / x-ui / multiline
```
Added value: +true
```
Changed1 schema field changedSep 26, 2026
- addedInput schema / properties / text / x-ui
```
Added value: +{
+  "unset_label": "Uses the attached file instead"
+}
```
Changed1 schema field changedSep 25, 2026
- addedInput schema / x-require-one-of
```
Added value: +[
+  [
+    "file"
+  ],
+  [
+    "text"
+  ]
+]
```

Changed5 schema fields changedSep 11, 2026

changedInput schema / properties / file / description

Previous value: -"PDF or HTML file. Other types (incl. DOCX) are scanned as raw bytes and usually yield few links."New value: +"A PDF or HTML file to pull the links out of. Any other type is read as plain text."

addedInput schema / properties / file / title
```
Added value: +"File to scan"
```

changedInput schema / properties / text / description

Previous value: -"Direct text/HTML alternative to the file."New value: +"Paste text or HTML to pull links out of. Ignored if a file is attached — the file wins."

addedInput schema / properties / text / title
```
Added value: +"Text or HTML to scan"
```

changedInput schema / required

Previous value: -[
-  "file"
-]New value: +[]

First observedSep 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With readOnlyHint=true, the safety profile is already known, while the description adds behavioral context: PDF/HTML are parsed for hyperlinks and other file types are scanned as raw text. This goes beyond the annotations without contradicting them.

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?

The description is two tight phrases plus a category tag, with the main behavior front-loaded and no filler. Every sentence contributes to understanding inputs and behavior.

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 simple two-parameter, read-only extractor this is nearly complete: it explains input types, text/file precedence in the schema, and fallback scanning. It doesn't describe the exact return shape, but 'extract all hyperlinks' sufficiently implies a list of links.

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 parameters are named and documented well, including the file-wins precedence. The description mostly restates what the schema already says, so it doesn't add significant parameter-level meaning.

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 opens with 'Extract all hyperlinks from a PDF or HTML file, or from pasted text,' giving a specific verb, resource, and accepted source types. It also distinguishes itself from the long analyze_* sibling list by specifying files/text rather than general analysis.

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 clearly indicates the tool is for link extraction from PDF/HTML/text and notes the fallback behavior for other file types. It doesn't explicitly name alternative tools or exclusion conditions, so it stops short of a 5.

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

All John's Essentials tools Inspect

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

Need Help?