HirePulse MCP

Web Page to Markdown

url_to_clean_markdown

Read-only

Convert a public web page URL into clean Markdown with scripts, navigation and ads removed, plus title, meta description and token estimate.

Instructions

Public web page to clean Markdown with title, meta description and a token estimate; scripts, navigation and ads removed. max_chars 1 to 100000 (default 15000). $0.002; empty results are free.

Input Schema

Name	Required	Description
`url`	Yes	Public HTTP(S) page URL to convert to Markdown; private addresses, unsafe redirects and credential-bearing URLs are rejected.
`context`	No	Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.
`max_chars`	No	Maximum characters of Markdown to return; longer pages are truncated and marked as such.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.0.0Oct 27, 2026

addedInput schema / properties / context

Added value: +{
+  "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+  "type": "string"
+}

addedInput schema / properties / max_chars / description

Added value: +"Maximum characters of Markdown to return; longer pages are truncated and marked as such."

addedInput schema / properties / url / description

Added value: +"Public HTTP(S) page URL to convert to Markdown; private addresses, unsafe redirects and credential-bearing URLs are rejected."

addedOutput schema / anyOf

Added value: +[
+  {
+    "properties": {
+      "domain": {
+        "type": "string"
+      },
+      "markdown": {
+        "type": "string"
+      },
+      "meta_description": {
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      },
+      "token_count_estimate": {
+        "type": "integer"
+      },
+      "truncated": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "domain",
+      "status"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {
+      "code": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "status": {
+        "maximum": 599,
+        "minimum": 400,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "status",
+      "code"
+    ],
+    "type": "object"
+  }
+]

removedOutput schema / properties

Removed value: -{
-  "domain": {
-    "type": "string"
-  },
-  "markdown": {
-    "type": "string"
-  },
-  "meta_description": {
-    "type": "string"
-  },
-  "status": {
-    "type": "string"
-  },
-  "title": {
-    "type": "string"
-  },
-  "token_count_estimate": {
-    "type": "integer"
-  },
-  "truncated": {
-    "type": "boolean"
-  }
-}

removedOutput schema / required

Removed value: -[
-  "domain",
-  "status"
-]

First observedv0.1.0Oct 21, 2026

TDQS

A4.1/5.0

Behavior5/5

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

The description adds substantial behavior beyond the annotations: it says scripts, navigation, and ads are removed; title, meta description, and token estimate are included; truncation is marked; and pricing is $0.002 with empty results free. These details are highly useful for an agent deciding whether and how to call the tool.

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 a single dense sentence that front-loads the core operation and then adds the most decision-relevant constraints: output cleanliness, max_chars range, and cost. Every clause carries useful information.

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

Completeness5/5

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

Given 100% schema coverage, an output schema, and annotations covering read-only/open-world behavior, the description supplies the remaining decision-critical context: public-page scope, cleaning behavior, truncation, token estimate, and pricing. An agent has enough information to call it correctly.

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%, so the schema already documents url, context, and max_chars thoroughly. The description restates max_chars bounds and default and adds the pricing note, but it does not add parameter meaning beyond what the schema provides; baseline 3 is appropriate.

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?

The description clearly states that it converts a public web page into clean Markdown, including title, meta description, and token estimate, while removing scripts, navigation, and ads. It is specific about the operation and output traits, but it does not distinguish itself from possible sibling URL-conversion tools such as universal_product_url_to_json.

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?

The word 'Public' implies that private pages are out of scope, and the pricing note helps frame usage economics. However, there is no explicit when-to-use guidance, no stated alternatives, and no when-not-to-use conditions beyond the public-page constraint.

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