Skip to main content
Glama
MissionSquad

@missionsquad/mcp-searxng-puppeteer

Official

get_url_content

Extract and retrieve web page content from any URL to analyze information for further processing.

Instructions

Get the content of a URL. Use this for further information retrieving to understand the content of each URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL

Implementation Reference

  • Handler logic for the 'get_url_content' tool. Extracts URL from arguments, checks Puppeteer scraper readiness, fetches content using helper function, and returns markdown text.
    if (name === "get_url_content") {
      if (!scraperReady) {
        return {
          content: [
            {
              type: 'text',
              text: 'Tool not ready: Puppeteer is still initializing. Please try again in a few moments.'
            }
          ],
          isError: true
        }
      }
      const { url } = args
      const result = await fetchAndConvertToMarkdown(url as string)
      return {
        content: [{ type: 'text', text: result }],
        isError: false
      }
    }
  • Schema definition for the 'get_url_content' tool, including name, description, and input schema requiring a 'url' parameter.
    const READ_URL_TOOL: Tool = {
      name: "get_url_content",
      description:
        "Get the content of a URL. " +
        "Use this for further information retrieving to understand the content of each URL.",
      inputSchema: {
        type: "object",
        properties: {
          url: {
            type: "string",
            description: "URL",
          },
        },
        required: ["url"],
      },
    };
  • index.ts:88-96 (registration)
    Registration of the 'get_url_content' tool in the MCP server capabilities alongside web_search.
      web_search: {
        description: WEB_SEARCH_TOOL.description,
        schema: WEB_SEARCH_TOOL.inputSchema,
      },
      get_url_content: {
        description: READ_URL_TOOL.description,
        schema: READ_URL_TOOL.inputSchema,
      },
    },
  • Helper function implementing the core logic: scrapes the URL using PuppeteerScraper instance and returns the text content (assumed markdown). Invoked by the handler.
    async function fetchAndConvertToMarkdown(url: string, timeoutMs: number = 10000) {
      if (!scraperReady || !scraper) {
        throw new Error('Puppeteer is not ready. Please try again in a few moments.')
      }
    
      try {
        const response = await scraper.scrapePage(url)
    
        if (response == null) {
          throw new Error(`Failed to fetch the URL: ${url}`)
        }
    
        const { content } = response
        return content.text
      } catch (error: any) {
        console.error('Error during scrape:', error.message)
        throw error
      }
    }
  • index.ts:246-248 (registration)
    Registration of the ListTools handler which exposes 'get_url_content' via READ_URL_TOOL in the tools list.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [WEB_SEARCH_TOOL, READ_URL_TOOL],
    }));
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 tool retrieves content but lacks details on behavioral traits like error handling (e.g., for invalid URLs), authentication needs, rate limits, or output format (e.g., text, HTML). This leaves significant gaps for an agent to understand how the tool behaves in practice.

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 appropriately sized and front-loaded: the first sentence states the core purpose, and the second provides usage context. Both sentences earn their place by adding value without redundancy, making it efficient and easy to parse for an agent.

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?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is moderately complete. It covers purpose and usage but lacks details on behavioral aspects like error handling or output format, which are important for a content retrieval tool. Without annotations or output schema, more context would improve completeness.

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 100% description coverage, with the 'url' parameter documented as 'URL'. The description adds no additional meaning beyond this, as it doesn't specify URL format constraints (e.g., must be valid HTTP/HTTPS) or usage examples. With high schema coverage, the baseline is 3, and the description doesn't compensate with extra insights.

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 tool's purpose: 'Get the content of a URL' specifies the verb (get) and resource (URL content). It distinguishes from the sibling 'web_search' by focusing on retrieving content from a specific URL rather than searching the web. However, it doesn't specify the exact nature of the content (e.g., HTML, text, metadata), which prevents a perfect score.

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?

The description provides clear usage context: 'Use this for further information retrieving to understand the content of each URL' indicates when to use it—for analyzing URL content. It implicitly distinguishes from 'web_search' by focusing on specific URLs rather than search queries. However, it lacks explicit exclusions or alternatives, such as when not to use it (e.g., for invalid URLs or rate-limited sites).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MissionSquad/mcp-searxng'

If you have feedback or need assistance with the MCP directory API, please join our Discord server