Markdownify MCP Server

bing-search-to-markdown

Convert Bing search results pages into Markdown format for easy reading and integration into documents.

Instructions

Convert a Bing search results page to markdown

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": "bing-search-to-markdown"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	URL of the Bing search results page

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.1Jan 24, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Convert') but doesn't explain what the conversion entails (e.g., formatting, extraction of specific elements), potential errors (e.g., invalid URLs), or output characteristics (e.g., markdown structure). This leaves significant gaps in understanding the tool's behavior.

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, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly without unnecessary details.

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 lack of annotations and output schema, the description is incomplete. It doesn't address key aspects like what the markdown output includes (e.g., search results, metadata), error handling, or how it differs from sibling tools, leaving the agent with insufficient context for reliable use.

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 schema description coverage is 100%, with the parameter 'url' clearly documented in the input schema. The description doesn't add any additional meaning beyond this, such as URL format requirements or examples, but the schema provides adequate baseline information, justifying a score of 3.

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 the verb ('Convert') and resource ('Bing search results page'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'webpage-to-markdown' or 'get-markdown-file', which could cause confusion about when to use this specific tool versus similar alternatives.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'webpage-to-markdown' that might handle general webpages, the description lacks context on prerequisites (e.g., requiring a Bing search URL) or exclusions, leaving the agent to guess based on the tool name alone.

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

Deploy Server