Skip to main content
Glama

Extract web links

bpj_extract_web_links
Read-onlyIdempotent

Extract and deduplicate absolute HTTP and HTTPS URLs in first-seen order.

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": {
      "text": "<text>"
    },
    "name": "bpj_extract_web_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description still contributes real behavior: deduplication semantics and first-seen output ordering, plus the 'absolute' qualifier implying relative and non-HTTP references are dropped. It stops short of stating the result container or what an empty result looks like.

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?

One front-loaded sentence with zero filler; the noun phrase and ordering rule are packed tightly with no redundancy.

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

Completeness3/5

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

The tool is simple and has no output schema, so the description should still say what is returned (array of URL strings vs. an object) and how edge cases behave. Dedup and ordering are covered, but return shape and the length-limit behavior are not.

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 coverage is 0% for the single `text` parameter, so the description must carry the burden. It implicitly defines the input as the text to scan, but adds nothing about the 12000-character cap, multi-line handling, or whether markdown/code blocks are scanned.

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?

Two specific verbs (extract, deduplicate) applied to a precisely scoped resource (absolute HTTP/HTTPS URLs) with an ordering rule. This clearly separates it from generic text utilities such as bpj_deduplicate_lines or bpj_canonical_link_check, though no sibling is named.

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 when-to-use or when-not-to-use guidance, no mention of alternatives for related tasks (link checking, canonicalization, line dedup), and no stated preconditions for the input text. The purpose implies a use case, but the agent gets no routing help.

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.